From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-doc/eclass-manpages/
Date: Wed, 29 Mar 2023 11:38:32 +0000 (UTC) [thread overview]
Message-ID: <1680089879.e7c7a3483ec4e7fd82c3b4e39ea75fecc59067b7.sam@gentoo> (raw)
commit: e7c7a3483ec4e7fd82c3b4e39ea75fecc59067b7
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 29 11:37:59 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Mar 29 11:37:59 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e7c7a348
app-doc/eclass-manpages: update upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-doc/eclass-manpages/metadata.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-doc/eclass-manpages/metadata.xml b/app-doc/eclass-manpages/metadata.xml
index 2689e88fc39c..6b7923d93827 100644
--- a/app-doc/eclass-manpages/metadata.xml
+++ b/app-doc/eclass-manpages/metadata.xml
@@ -13,6 +13,6 @@
<name>Gentoo Portage tools team</name>
</maintainer>
<upstream>
- <remote-id type="github">projg2/eclass-manpages</remote-id>
+ <remote-id type="github">projg2/eclass-to-manpage</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2023-03-29 11:38 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 11:38 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-06 8:55 [gentoo-commits] repo/gentoo:master commit in: app-doc/eclass-manpages/ Sam James
2025-01-05 1:05 Sam James
2024-12-10 4:55 Sam James
2024-11-17 5:30 Sam James
2024-11-17 5:30 Sam James
2024-11-15 21:31 Sam James
2024-11-11 13:08 Sam James
2024-11-09 7:11 Sam James
2024-11-01 1:10 Matt Turner
2024-10-15 1:37 Sam James
2024-09-01 11:05 Sam James
2024-08-11 23:07 Sam James
2024-06-14 10:52 Sam James
2024-06-14 10:52 Sam James
2024-05-12 23:26 Sam James
2024-04-23 21:43 Sam James
2024-04-23 21:10 Sam James
2024-02-29 7:52 Sam James
2024-02-29 7:52 Sam James
2024-02-07 0:51 Sam James
2023-09-19 19:50 Sam James
2023-06-24 5:02 Sam James
2023-06-24 5:02 Sam James
2023-06-01 1:37 Sam James
2023-06-01 1:37 Sam James
2023-05-30 3:44 Sam James
2023-05-12 23:31 Sam James
2023-04-17 21:19 Sam James
2023-04-17 21:19 Sam James
2023-03-29 2:05 Sam James
2023-03-29 2:05 Sam James
2023-03-09 7:38 Arthur Zamarin
2023-02-22 14:48 Sam James
2023-01-10 6:17 Sam James
2022-09-25 4:39 Sam James
2022-09-25 4:39 Sam James
2022-08-24 21:24 Sam James
2022-07-25 8:56 Ulrich Müller
2022-07-25 8:56 Ulrich Müller
2022-07-25 8:56 Ulrich Müller
2022-07-25 8:56 Ulrich Müller
2022-07-16 19:57 Sam James
2022-07-16 19:57 Sam James
2022-04-17 20:34 Ulrich Müller
2022-04-17 20:34 Ulrich Müller
2022-03-16 17:33 Sam James
2022-03-16 17:33 Sam James
2021-10-02 9:56 Ulrich Müller
2021-10-02 9:55 Ulrich Müller
2021-10-02 9:55 Ulrich Müller
2021-07-12 14:24 Ulrich Müller
2021-07-12 14:24 Ulrich Müller
2021-07-12 14:24 Ulrich Müller
2021-01-04 11:04 Ulrich Müller
2021-01-04 11:04 Ulrich Müller
2020-09-13 18:48 Ulrich Müller
2020-09-13 18:48 Ulrich Müller
2020-07-04 6:51 Michał Górny
2020-02-13 17:09 Ulrich Müller
2019-12-22 11:56 Ulrich Müller
2019-12-15 12:31 Ulrich Müller
2019-12-15 12:31 Ulrich Müller
2019-11-06 8:45 Michał Górny
2019-11-06 8:45 Michał Górny
2019-09-08 6:43 Michał Górny
2019-09-08 6:43 Michał Górny
2019-07-28 8:25 Michał Górny
2019-07-28 6:41 Michał Górny
2019-07-14 6:56 Michał Górny
2019-06-05 6:53 Michał Górny
2019-06-02 6:40 Michał Górny
2019-03-29 8:57 Mikle Kolyada
2019-03-29 8:49 Michał Górny
2019-03-29 8:16 Michał Górny
2019-03-19 6:08 Michał Górny
2019-03-14 12:47 Michał Górny
2019-03-14 12:39 Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1680089879.e7c7a3483ec4e7fd82c3b4e39ea75fecc59067b7.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox