From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/tempest/
Date: Sun, 5 Jun 2022 05:52:59 +0000 (UTC) [thread overview]
Message-ID: <1654408237.652b0df5f582c8d01033a9272adf3f70bf6946ec.mgorny@gentoo> (raw)
commit: 652b0df5f582c8d01033a9272adf3f70bf6946ec
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 5 05:50:37 2022 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Jun 5 05:50:37 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=652b0df5
dev-python/tempest: Add python@ as co-maint.
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/tempest/metadata.xml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/dev-python/tempest/metadata.xml b/dev-python/tempest/metadata.xml
index b260fb53bd80..8e745082126b 100644
--- a/dev-python/tempest/metadata.xml
+++ b/dev-python/tempest/metadata.xml
@@ -5,6 +5,10 @@
<email>arthurzam@gentoo.org</email>
<name>Arthur Zamarin</name>
</maintainer>
+ <maintainer type="project">
+ <email>python@gentoo.org</email>
+ <name>Python</name>
+ </maintainer>
<stabilize-allarches/>
<upstream>
<remote-id type="pypi">tempest</remote-id>
next reply other threads:[~2022-06-05 5:53 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 5:52 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-28 12:59 [gentoo-commits] repo/gentoo:master commit in: dev-python/tempest/ Michał Górny
2024-09-28 12:32 Arthur Zamarin
2024-09-26 4:50 Michał Górny
2024-09-10 7:06 Michał Górny
2024-06-20 8:45 Petr Vaněk
2024-06-08 9:02 Michał Górny
2024-06-08 7:28 Arthur Zamarin
2024-05-24 4:03 Michał Górny
2024-04-13 17:49 Michał Górny
2024-04-13 16:39 Arthur Zamarin
2024-03-29 15:28 Michał Górny
2024-03-07 17:09 Michał Górny
2024-03-07 16:24 Michał Górny
2024-02-19 15:51 Michał Górny
2023-11-08 9:11 Michał Górny
2023-11-02 5:44 Michał Górny
2023-11-02 4:12 Sam James
2023-09-27 16:48 Arthur Zamarin
2023-07-10 1:48 Michał Górny
2023-07-09 16:51 Arthur Zamarin
2023-06-09 12:22 Michał Górny
2023-06-06 5:57 Michał Górny
2023-06-06 1:51 Sam James
2023-05-06 16:44 Arthur Zamarin
2023-04-05 8:17 Michał Górny
2023-04-05 7:10 Arthur Zamarin
2023-03-21 20:06 Michał Górny
2023-03-01 6:16 Michał Górny
2023-02-28 18:16 Arthur Zamarin
2023-01-08 5:12 Michał Górny
2023-01-08 5:06 Michał Górny
2023-01-07 18:36 Arthur Zamarin
2022-12-08 16:57 Michał Górny
2022-10-22 16:00 Michał Górny
2022-10-22 15:56 Arthur Zamarin
2022-09-18 16:11 Arthur Zamarin
2022-08-03 7:04 Michał Górny
2022-08-02 20:27 Sam James
2022-07-15 13:45 Arthur Zamarin
2022-07-04 7:14 Michał Górny
2022-07-04 6:51 Agostino Sarubbo
2022-06-30 17:09 Arthur Zamarin
2022-06-03 5:37 Michał Górny
2022-05-28 21:12 Jakov Smolić
2022-04-11 16:07 Michał Górny
2022-04-01 18:45 Michał Górny
2022-04-01 17:29 Arthur Zamarin
2022-03-14 21:00 Arthur Zamarin
2022-02-24 18:08 Michał Górny
2021-12-22 19:44 Arthur Zamarin
2021-12-17 9:15 Michał Górny
2021-12-10 15:44 Arthur Zamarin
2021-12-10 12:01 Jakov Smolić
2021-11-19 6:18 Arthur Zamarin
2021-11-12 19:00 Arthur Zamarin
2021-11-05 7:44 Arthur Zamarin
2021-10-31 17:58 Sam James
2021-10-31 17:55 Sam James
2021-10-04 22:58 Sam James
2021-10-01 12:25 Arthur Zamarin
2021-09-30 17:59 Arthur Zamarin
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=1654408237.652b0df5f582c8d01033a9272adf3f70bf6946ec.mgorny@gentoo \
--to=mgorny@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