From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/elasticsearch-curator/
Date: Sun, 2 Oct 2016 12:59:28 +0000 (UTC) [thread overview]
Message-ID: <1475413114.67cf7a180de954a218678eda0a1ade229369bb76.gokturk@gentoo> (raw)
commit: 67cf7a180de954a218678eda0a1ade229369bb76
Author: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 2 12:51:04 2016 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Sun Oct 2 12:58:34 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=67cf7a18
dev-python/elasticsearch-curator: add proxy-maint back as a maintainer
Please do not remove projects/developers from the metadata without
consulting them first. Thank you!
Package-Manager: portage-2.3.0
dev-python/elasticsearch-curator/metadata.xml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/dev-python/elasticsearch-curator/metadata.xml b/dev-python/elasticsearch-curator/metadata.xml
index 63b673e..32b8b78 100644
--- a/dev-python/elasticsearch-curator/metadata.xml
+++ b/dev-python/elasticsearch-curator/metadata.xml
@@ -13,6 +13,10 @@
<email>erkiferenc@gmail.com</email>
<name>Ferenc Erki</name>
</maintainer>
+ <maintainer type="project">
+ <email>proxy-maint@gentoo.org</email>
+ <name>Proxy Maintainers</name>
+ </maintainer>
<upstream>
<remote-id type="github">elasticsearch/curator</remote-id>
</upstream>
next reply other threads:[~2016-10-02 12:59 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 12:59 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-09 9:44 [gentoo-commits] repo/gentoo:master commit in: dev-python/elasticsearch-curator/ Sam James
2021-03-09 9:44 Sam James
2020-12-23 1:17 Thomas Deutschmann
2020-12-11 14:51 Michał Górny
2020-12-10 19:31 Thomas Deutschmann
2020-06-30 6:34 Agostino Sarubbo
2020-05-25 12:18 Mikle Kolyada
2020-04-23 13:06 Michał Górny
2020-03-27 8:58 Michał Górny
2019-10-28 14:43 Joonas Niilola
2019-08-16 13:50 Michał Górny
2018-12-17 1:03 Thomas Deutschmann
2018-11-17 14:27 Mikle Kolyada
2018-11-15 15:48 Thomas Deutschmann
2018-10-12 0:57 Thomas Deutschmann
2018-10-12 0:57 Thomas Deutschmann
2018-07-11 8:13 Tony Vroon
2018-05-11 8:35 Michał Górny
2018-05-11 8:35 Michał Górny
2018-04-23 14:32 Aaron Bauman
2018-01-31 22:10 Michał Górny
2018-01-31 22:10 Michał Górny
2017-11-30 14:47 Patrice Clement
2017-11-30 14:47 Patrice Clement
2017-11-13 15:41 Manuel Rüger
2017-11-07 22:59 Patrice Clement
2017-10-29 21:08 Thomas Deutschmann
2017-09-10 21:24 Patrice Clement
2017-09-10 21:24 Patrice Clement
2017-09-10 21:24 Patrice Clement
2017-08-14 21:41 Patrice Clement
2017-08-14 21:41 Patrice Clement
2017-07-08 21:35 Patrice Clement
2017-06-20 5:17 Agostino Sarubbo
2017-06-19 17:03 Agostino Sarubbo
2017-05-24 13:27 Michał Górny
2017-05-19 10:52 Michał Górny
2017-05-18 22:25 Michał Górny
2017-05-17 16:37 Patrick Lauer
2017-02-06 21:14 Göktürk Yüksek
2017-01-26 8:31 Göktürk Yüksek
2017-01-26 8:31 Göktürk Yüksek
2016-12-27 18:44 Göktürk Yüksek
2016-10-28 19:45 Patrick Lauer
2016-09-29 20:42 Patrice Clement
2016-09-02 5:26 Patrick Lauer
2016-08-16 17:59 Patrice Clement
2016-08-09 9:44 Patrick Lauer
2016-07-08 19:05 Patrice Clement
2016-07-08 19:05 Patrice Clement
2016-03-23 14:59 Patrick Lauer
2016-03-18 13:43 Patrice Clement
2016-03-18 12:23 Ian Delaney
2016-03-17 14:27 Patrick Lauer
2016-02-15 13:16 Patrice Clement
2016-02-15 13:16 Patrice Clement
2016-02-15 13:16 Patrice Clement
2015-11-23 11:32 Ian Delaney
2015-11-12 8:18 Ian Delaney
2015-11-11 14:15 Ian Delaney
2015-09-11 7:53 Justin Lecher
2015-09-10 6:26 Ian Delaney
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=1475413114.67cf7a180de954a218678eda0a1ade229369bb76.gokturk@gentoo \
--to=gokturk@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