From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/cryfs/
Date: Sun, 1 Sep 2024 02:39:53 +0000 (UTC) [thread overview]
Message-ID: <1725158360.1d6ef0c952f63e2d848f93690ba7bf285fb64425.dlan@gentoo> (raw)
commit: 1d6ef0c952f63e2d848f93690ba7bf285fb64425
Author: Nicholas Meyer <nickaristocrates <AT> gmail <DOT> com>
AuthorDate: Sat Aug 31 15:24:22 2024 +0000
Commit: Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Sun Sep 1 02:39:20 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1d6ef0c9
sys-fs/cryfs: remove proxied maintainer
Bug: https://bugs.gentoo.org/718000
Closes: https://github.com/gentoo/gentoo/pull/38359
Signed-off-by: Nicholas Meyer <nickaristocrates <AT> gmail.com>
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>
sys-fs/cryfs/metadata.xml | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/sys-fs/cryfs/metadata.xml b/sys-fs/cryfs/metadata.xml
index dce6d653fddc..bc16b23e5ab2 100644
--- a/sys-fs/cryfs/metadata.xml
+++ b/sys-fs/cryfs/metadata.xml
@@ -1,14 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person" proxied="yes">
- <email>nickaristocrates@gmail.com</email>
- <name>Nicholas Meyer</name>
- </maintainer>
- <maintainer type="project" proxied="proxy">
- <email>proxy-maint@gentoo.org</email>
- <name>Proxy Maintainers</name>
- </maintainer>
+ <!-- maintainer-needed -->
<upstream>
<remote-id type="github">cryfs/cryfs</remote-id>
</upstream>
next reply other threads:[~2024-09-01 2:39 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 2:39 Yixun Lan [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-05 12:00 [gentoo-commits] repo/gentoo:master commit in: sys-fs/cryfs/ Sam James
2025-04-29 20:36 Mike Gilbert
2025-02-15 9:29 Ulrich Müller
2025-01-24 8:14 Sam James
2024-08-30 13:15 Arthur Zamarin
2024-06-03 11:15 Sam James
2024-03-03 17:33 Andreas K. Hüttel
2024-02-28 22:57 Sam James
2023-06-27 7:06 Sam James
2023-04-26 4:03 Sam James
2023-01-23 2:40 Sam James
2022-09-04 13:03 David Seifert
2022-06-28 4:18 WANG Xuerui
2022-04-18 18:56 Alexey Shvetsov
2021-10-14 6:38 Andreas Sturmlechner
2021-10-13 20:33 Sam James
2021-08-29 10:02 Agostino Sarubbo
2021-08-18 0:35 Yixun Lan
2021-08-13 18:33 Sam James
2021-08-13 18:33 Sam James
2021-05-10 9:45 Sam James
2021-05-02 17:47 Mikle Kolyada
2021-01-18 8:55 Joonas Niilola
2020-11-05 12:32 Joonas Niilola
2020-11-05 12:32 Joonas Niilola
2020-10-16 11:12 Georgy Yakovlev
2020-06-04 20:57 Andreas Sturmlechner
2020-05-16 7:09 Joonas Niilola
2020-05-16 7:09 Joonas Niilola
2020-04-17 15:56 Andreas Sturmlechner
2020-02-10 13:26 Michał Górny
2020-01-18 23:09 Andreas Sturmlechner
2020-01-18 23:09 Andreas Sturmlechner
2020-01-18 23:09 Andreas Sturmlechner
2019-11-13 2:51 Aaron Bauman
2019-11-02 8:42 Agostino Sarubbo
2019-11-01 23:51 Thomas Deutschmann
2019-11-01 8:53 Andreas Sturmlechner
2019-10-26 21:14 Andreas Sturmlechner
2019-10-26 21:06 Andreas Sturmlechner
2019-10-26 20:15 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-05-28 2:35 Aaron Bauman
2019-02-19 18:04 Andreas Sturmlechner
2018-09-24 1:50 Thomas Deutschmann
2018-09-16 17:51 Mikle Kolyada
2018-08-11 17:03 Mike Gilbert
2018-04-11 22:47 Patrice Clement
2018-03-15 20:17 Markus Meier
2018-01-21 5:03 Michael Palimaka
2018-01-18 16:07 Mikle Kolyada
2018-01-17 11:01 Andreas Sturmlechner
2017-10-11 19:15 Johannes Huber
2017-10-11 19:15 Johannes Huber
2017-10-11 19:15 Johannes Huber
2017-05-27 13:48 Michał Górny
2017-05-27 13:48 Michał Górny
2017-05-24 17:12 Michał Górny
2017-05-24 17:12 Michał Górny
2017-05-24 17:04 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=1725158360.1d6ef0c952f63e2d848f93690ba7bf285fb64425.dlan@gentoo \
--to=dlan@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