From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/etckeeper/
Date: Fri, 13 Dec 2024 05:07:05 +0000 (UTC) [thread overview]
Message-ID: <1734066076.2e852fa30e79ee87755bb5f1f96e6ba477b8a870.sam@gentoo> (raw)
commit: 2e852fa30e79ee87755bb5f1f96e6ba477b8a870
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 13 05:01:16 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Dec 13 05:01:16 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2e852fa3
sys-apps/etckeeper: remove github upstream metadata
Joey moved off GH a while ago.
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-apps/etckeeper/metadata.xml | 3 ---
1 file changed, 3 deletions(-)
diff --git a/sys-apps/etckeeper/metadata.xml b/sys-apps/etckeeper/metadata.xml
index 838d76fac7fd..3b40288025ac 100644
--- a/sys-apps/etckeeper/metadata.xml
+++ b/sys-apps/etckeeper/metadata.xml
@@ -11,7 +11,4 @@
file metadata that revison control systems do not normally support, but that
is important for /etc, such as the permissions of /etc/shadow.
</longdescription>
- <upstream>
- <remote-id type="github">joeyh/etckeeper</remote-id>
- </upstream>
</pkgmetadata>
next reply other threads:[~2024-12-13 5:07 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 5:07 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-14 7:11 [gentoo-commits] repo/gentoo:master commit in: sys-apps/etckeeper/ Petr Vaněk
2025-04-13 21:22 Sam James
2025-03-27 11:49 Sam James
2025-03-27 11:49 Sam James
2025-03-27 11:49 Sam James
2025-03-27 11:49 Sam James
2025-03-27 11:03 Sam James
2025-02-24 11:21 Petr Vaněk
2024-12-13 5:07 Sam James
2024-06-04 17:49 Viorel Munteanu
2024-05-19 17:49 Arthur Zamarin
2024-05-19 17:09 Sam James
2024-05-19 17:09 Sam James
2024-05-19 17:06 Arthur Zamarin
2024-05-19 17:02 Arthur Zamarin
2023-11-30 3:07 Sam James
2023-07-08 3:39 Sam James
2023-07-07 10:14 Sam James
2023-07-07 4:40 Sam James
2023-07-07 4:40 Sam James
2023-07-07 4:40 Sam James
2023-07-07 3:36 Sam James
2022-11-01 15:47 Arthur Zamarin
2022-11-01 8:44 Agostino Sarubbo
2022-11-01 8:29 Agostino Sarubbo
2022-11-01 8:28 Agostino Sarubbo
2022-11-01 8:26 Agostino Sarubbo
2022-11-01 6:51 Georgy Yakovlev
2022-10-01 5:36 Sam James
2022-06-05 23:03 Conrad Kostecki
2022-05-20 4:01 Georgy Yakovlev
2022-05-05 12:01 Jakov Smolić
2022-03-27 2:33 Sam James
2022-03-18 12:26 Arthur Zamarin
2022-03-15 16:27 Sam James
2021-11-20 7:32 Georgy Yakovlev
2021-11-20 7:28 Agostino Sarubbo
2021-11-19 8:10 Agostino Sarubbo
2021-11-19 6:18 Arthur Zamarin
2021-11-19 2:43 Sam James
2021-07-22 22:25 Marek Szuba
2021-07-10 2:12 Georgy Yakovlev
2020-11-24 6:06 Georgy Yakovlev
2020-03-31 10:01 Agostino Sarubbo
2020-03-31 7:23 Georgy Yakovlev
2020-03-31 7:18 Agostino Sarubbo
2020-01-08 11:27 Georgy Yakovlev
2018-10-13 22:02 Patrice Clement
2018-10-03 5:15 Georgy Yakovlev
2018-10-01 3:54 Benda XU
2018-09-24 18:48 Mikle Kolyada
2018-04-23 14:50 Aaron Bauman
2018-04-05 21:33 Michał Górny
2018-04-05 21:33 Michał Górny
2018-04-05 21:33 Michał Górny
2017-11-21 18:00 Manuel Rüger
2017-05-28 21:18 Manuel Rüger
2016-08-06 13:34 Manuel Rüger
2016-08-06 13:27 Manuel Rüger
2016-07-16 22:31 Manuel Rüger
2016-03-15 15:27 Agostino Sarubbo
2016-03-06 12:58 Agostino Sarubbo
2016-02-15 23:22 Manuel Rüger
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=1734066076.2e852fa30e79ee87755bb5f1f96e6ba477b8a870.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