From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pickleshare/
Date: Wed, 10 Jun 2020 08:11:26 +0000 (UTC) [thread overview]
Message-ID: <1591776669.981e06f5afe8ab102163f3474e117cd48e14c069.mgorny@gentoo> (raw)
commit: 981e06f5afe8ab102163f3474e117cd48e14c069
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 10 08:08:22 2020 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Jun 10 08:11:09 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=981e06f5
dev-python/pickleshare: Add python@ as (co-)maint
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/pickleshare/metadata.xml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/dev-python/pickleshare/metadata.xml b/dev-python/pickleshare/metadata.xml
index 5d8abb4a353..f433b9658f4 100644
--- a/dev-python/pickleshare/metadata.xml
+++ b/dev-python/pickleshare/metadata.xml
@@ -5,6 +5,10 @@
<email>sci@gentoo.org</email>
<name>Gentoo Science Project</name>
</maintainer>
+ <maintainer type="project">
+ <email>python@gentoo.org</email>
+ <name>Python</name>
+ </maintainer>
<longdescription>
Like shelve, a PickleShareDB object acts like a normal dictionary.
Unlike shelve, many processes can access the database
next reply other threads:[~2020-06-10 8:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 8:11 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-20 17:09 [gentoo-commits] repo/gentoo:master commit in: dev-python/pickleshare/ Michał Górny
2024-05-18 6:58 Michał Górny
2023-11-16 19:43 Michał Górny
2023-11-16 19:43 Michał Górny
2023-10-27 14:04 Michał Górny
2023-10-27 12:17 Sam James
2023-10-15 8:00 Sam James
2023-10-15 7:38 Sam James
2023-10-14 19:52 Arthur Zamarin
2023-10-14 18:17 Arthur Zamarin
2023-10-14 18:17 Arthur Zamarin
2023-10-14 16:52 Arthur Zamarin
2023-09-14 11:24 Andrew Ammerlaan
2022-09-22 7:45 Michał Górny
2022-05-16 14:43 Andrew Ammerlaan
2022-02-14 8:35 Matt Turner
2022-01-30 11:33 James Le Cuirot
2021-11-01 15:46 Sam James
2021-09-26 17:52 Sam James
2021-09-08 16:19 Sam James
2021-06-29 5:53 Yixun Lan
2021-05-06 11:38 Michał Górny
2020-06-08 17:36 Michał Górny
2020-06-03 18:43 Agostino Sarubbo
2020-06-02 22:21 Mart Raudsepp
2020-03-28 11:59 Michał Górny
2020-03-01 4:12 Andrey Grozin
2020-01-26 17:11 Michał Górny
2019-12-14 0:41 David Seifert
2018-05-27 8:44 Mart Raudsepp
2018-05-16 12:28 Agostino Sarubbo
2018-03-21 20:24 Markus Meier
2018-03-12 0:51 Matt Turner
2018-03-04 22:40 Sergei Trofimovich
2017-05-22 16:41 Michał Górny
2017-03-12 6:19 Zac Medico
2017-02-04 21:30 David Seifert
2016-10-19 23:22 Patrice Clement
2016-10-19 23:22 Patrice Clement
2016-07-30 8:28 David Seifert
2016-07-23 11:46 David Seifert
2016-02-28 6:51 Matt Thode
2016-01-21 8:33 Justin Lecher
2015-11-28 17:33 Justin Lecher
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=1591776669.981e06f5afe8ab102163f3474e117cd48e14c069.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