From: "Manuel Rüger" <mrueg@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/vcrpy/
Date: Sun, 23 Jul 2017 11:40:31 +0000 (UTC) [thread overview]
Message-ID: <1500810009.4e181d4846508788f204caf5c031e0683afcba3f.mrueg@gentoo> (raw)
commit: 4e181d4846508788f204caf5c031e0683afcba3f
Author: Manuel Rüger <mrueg <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 23 11:40:09 2017 +0000
Commit: Manuel Rüger <mrueg <AT> gentoo <DOT> org>
CommitDate: Sun Jul 23 11:40:09 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4e181d48
dev-python/vcrpy: Drop myself as maintainer
Package-Manager: Portage-2.3.6, Repoman-2.3.3
dev-python/vcrpy/metadata.xml | 4 ----
1 file changed, 4 deletions(-)
diff --git a/dev-python/vcrpy/metadata.xml b/dev-python/vcrpy/metadata.xml
index 8380375c8f8..625f4389c4a 100644
--- a/dev-python/vcrpy/metadata.xml
+++ b/dev-python/vcrpy/metadata.xml
@@ -1,10 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person">
- <email>mrueg@gentoo.org</email>
- <name>Manuel Rüger</name>
- </maintainer>
<maintainer type="project">
<email>python@gentoo.org</email>
<name>Python</name>
next reply other threads:[~2017-07-23 11:40 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 11:40 Manuel Rüger [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-07 21:37 [gentoo-commits] repo/gentoo:master commit in: dev-python/vcrpy/ Sebastian Pipping
2024-08-24 13:11 Michał Górny
2024-08-24 10:45 Sam James
2024-08-03 14:33 Michał Górny
2024-06-28 19:20 Michał Górny
2024-02-11 11:11 Sam James
2024-01-26 5:39 Michał Górny
2024-01-23 18:18 Arthur Zamarin
2023-09-01 17:05 Michał Górny
2023-09-01 16:52 Arthur Zamarin
2023-07-31 7:13 Michał Górny
2023-07-28 9:26 Michał Górny
2023-07-28 7:56 Sam James
2023-06-27 12:03 Michał Górny
2023-06-27 6:43 Sam James
2023-06-27 6:43 Sam James
2023-06-26 22:31 Sebastian Pipping
2023-06-26 16:21 Sebastian Pipping
2023-05-26 16:45 Michał Górny
2023-05-26 13:29 Sebastian Pipping
2023-05-23 12:55 Sam James
2023-05-23 12:48 Sebastian Pipping
2022-12-17 6:40 WANG Xuerui
2022-10-03 6:36 Michał Górny
2022-10-02 19:24 Arthur Zamarin
2022-09-01 19:42 Arthur Zamarin
2022-08-02 19:05 Michał Górny
2022-08-02 18:47 Arthur Zamarin
2022-06-30 4:27 Michał Górny
2022-06-21 20:14 Michał Górny
2022-06-21 19:18 Arthur Zamarin
2022-05-18 6:59 Michał Górny
2022-05-18 6:59 Michał Górny
2021-07-02 18:59 Michał Górny
2021-05-31 10:43 Marek Szuba
2020-11-28 8:07 Sam James
2020-11-15 7:54 Michał Górny
2020-11-15 5:19 Sam James
2020-10-10 5:54 Michał Górny
2020-09-18 15:53 Michał Górny
2020-09-09 0:16 Sam James
2020-09-08 19:11 Michał Górny
2020-09-04 8:57 Sergei Trofimovich
2020-08-01 10:09 Michał Górny
2020-07-16 12:50 Sam James
2020-07-16 4:18 Sam James
2020-06-04 14:10 Sergei Trofimovich
2020-06-01 6:59 Sergei Trofimovich
2020-05-31 23:46 Matt Turner
2020-05-30 7:40 Michał Górny
2020-05-11 17:48 Michał Górny
2020-05-04 14:38 Agostino Sarubbo
2020-05-04 13:34 Agostino Sarubbo
2020-05-04 12:34 Michał Górny
2020-05-02 13:30 Mart Raudsepp
2020-04-08 14:05 Agostino Sarubbo
2020-04-08 14:01 Agostino Sarubbo
2020-04-08 13:36 Agostino Sarubbo
2020-04-08 12:46 Agostino Sarubbo
2020-04-07 7:03 Georgy Yakovlev
2020-03-19 13:25 Michał Górny
2020-03-17 8:08 Michał Górny
2019-12-29 8:53 David Seifert
2018-06-25 23:20 Thomas Deutschmann
2018-06-24 9:46 Pacho Ramos
2018-05-21 14:14 Sebastian Pipping
2017-07-23 11:54 Michael Palimaka
2017-05-30 13:38 Manuel Rüger
2017-05-15 16:44 Manuel Rüger
2017-05-02 8:47 Michał Górny
2017-04-15 21:36 Manuel Rüger
2017-01-23 18:16 Manuel Rüger
2017-01-21 18:54 Agostino Sarubbo
2016-12-20 15:19 Tobias Klausmann
2016-11-14 18:42 Manuel Rüger
2016-09-04 22:36 Manuel Rüger
2015-10-19 16:29 Justin Lecher
2015-09-16 8:53 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=1500810009.4e181d4846508788f204caf5c031e0683afcba3f.mrueg@gentoo \
--to=mrueg@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