From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pygdbmi/
Date: Sat, 2 Dec 2023 21:29:48 +0000 (UTC) [thread overview]
Message-ID: <1701552575.565c6543e226bb46c1ae70b5751aa96bb253ccaf.sam@gentoo> (raw)
commit: 565c6543e226bb46c1ae70b5751aa96bb253ccaf
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 2 21:28:15 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Dec 2 21:29:35 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=565c6543
dev-python/pygdbmi: update maintainers
I figure it makes sense to have a non-project maint first because otherwise
bugs are easier to miss.
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/pygdbmi/metadata.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/dev-python/pygdbmi/metadata.xml b/dev-python/pygdbmi/metadata.xml
index 5b3024573289..23ce86c5a4bc 100644
--- a/dev-python/pygdbmi/metadata.xml
+++ b/dev-python/pygdbmi/metadata.xml
@@ -1,9 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="project">
- <email>python@gentoo.org</email>
- </maintainer>
<maintainer type="person">
<email>parona@protonmail.com</email>
<name>Alfred Wingate</name>
@@ -12,6 +9,9 @@
<email>proxy-maint@gentoo.org</email>
<name>Proxy Maintainers</name>
</maintainer>
+ <maintainer type="project">
+ <email>python@gentoo.org</email>
+ </maintainer>
<stabilize-allarches/>
<upstream>
<remote-id type="github">cs01/pygdbmi</remote-id>
next reply other threads:[~2023-12-02 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 21:29 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-02 21:29 [gentoo-commits] repo/gentoo:master commit in: dev-python/pygdbmi/ Sam James
2023-12-02 21:29 Sam James
2024-05-18 7:26 Michał Górny
2024-07-23 19:15 Arthur Zamarin
2024-07-24 5:12 Sam James
2025-01-10 9:54 WANG Xuerui
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=1701552575.565c6543e226bb46c1ae70b5751aa96bb253ccaf.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