From: "Ian Delaney" <idella4@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/librsync/
Date: Fri, 18 Dec 2015 13:22:43 +0000 (UTC) [thread overview]
Message-ID: <1450441629.4041c22dd58d19d4ad1c4b2925439a03e8e0be52.idella4@gentoo> (raw)
commit: 4041c22dd58d19d4ad1c4b2925439a03e8e0be52
Author: Ian Delaney <idella4 <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 18 12:11:12 2015 +0000
Commit: Ian Delaney <idella4 <AT> gentoo <DOT> org>
CommitDate: Fri Dec 18 12:27:09 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4041c22d
net-libs/librsync: set new proxy maintainer in metadata
Documented offer by him made in the gentoo (security) bug #525396
Gentoo bug: #525396
Package-Manager: portage-2.2.24
net-libs/librsync/metadata.xml | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/net-libs/librsync/metadata.xml b/net-libs/librsync/metadata.xml
index 0453ebd..9abf884 100644
--- a/net-libs/librsync/metadata.xml
+++ b/net-libs/librsync/metadata.xml
@@ -1,10 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer>
- <email>maintainer-needed@gentoo.org</email>
- </maintainer>
- <upstream>
- <remote-id type="sourceforge">librsync</remote-id>
- </upstream>
+ <herd>proxy-maintainers</herd>
+ <maintainer>
+ <email>axelgenus@gmail.com</email>
+ <name>Alessandro Calorì</name>
+ <description>Proxied maintainer; set to assignee in all bugs</description>
+ </maintainer>
+ <upstream>
+ <remote-id type="sourceforge">librsync</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2015-12-18 13:22 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 13:22 Ian Delaney [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-25 17:31 [gentoo-commits] repo/gentoo:master commit in: net-libs/librsync/ Arthur Zamarin
2024-05-25 2:03 Sam James
2024-05-24 14:56 Arthur Zamarin
2024-05-24 14:56 Arthur Zamarin
2024-05-24 10:00 Arthur Zamarin
2024-05-24 10:00 Arthur Zamarin
2023-03-01 15:20 Joonas Niilola
2023-02-22 22:51 Bernard Cafarelli
2022-10-15 6:47 Jakov Smolić
2021-12-01 21:16 Andreas Sturmlechner
2021-12-01 13:31 Agostino Sarubbo
2021-11-29 17:34 Arthur Zamarin
2021-11-29 17:31 Jakov Smolić
2021-11-29 17:15 Arthur Zamarin
2021-11-29 17:15 Arthur Zamarin
2021-11-29 16:59 Arthur Zamarin
2021-11-27 16:55 David Seifert
2021-05-31 11:36 Bernard Cafarelli
2020-12-15 10:37 Sam James
2020-12-04 18:37 Sergei Trofimovich
2020-12-04 18:31 Sergei Trofimovich
2020-12-02 22:39 Sam James
2020-12-02 21:32 Sam James
2020-12-02 3:06 Thomas Deutschmann
2020-05-30 22:51 Bernard Cafarelli
2020-04-07 15:17 Bernard Cafarelli
2019-10-17 10:37 Bernard Cafarelli
2019-10-14 21:11 Bernard Cafarelli
2019-10-09 9:47 Bernard Cafarelli
2018-07-11 5:05 Markus Meier
2018-06-26 18:08 Bernard Cafarelli
2018-06-25 18:56 Tobias Klausmann
2018-06-24 14:45 Jason Zaman
2018-06-18 18:48 Jonas Stein
2018-06-16 15:04 Sergei Trofimovich
2018-06-13 20:36 Andreas Sturmlechner
2018-06-12 11:36 Thomas Deutschmann
2018-06-12 8:44 Sergei Trofimovich
2018-04-02 4:09 Matt Turner
2018-03-28 20:55 Matt Turner
2018-03-02 18:27 Michał Górny
2017-12-05 5:44 Markus Meier
2017-11-17 20:43 Sergei Trofimovich
2017-11-08 12:51 Tobias Klausmann
2017-10-29 21:58 Sergei Trofimovich
2017-10-29 20:58 Sergei Trofimovich
2017-10-24 19:23 Sergei Trofimovich
2017-10-22 20:33 Thomas Deutschmann
2017-10-19 12:43 Manuel Rüger
2017-01-29 19:33 Fabian Groffen
2016-02-22 6:06 Jeroen Roovers
2016-02-01 1:53 Patrice Clement
2016-01-17 17:02 Agostino Sarubbo
2016-01-11 9:07 Agostino Sarubbo
2016-01-10 10:34 Agostino Sarubbo
2016-01-09 16:06 Markus Meier
2016-01-09 7:10 Agostino Sarubbo
2016-01-06 17:54 Andreas Schuerch
2016-01-05 8:42 Agostino Sarubbo
2015-12-16 11:34 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=1450441629.4041c22dd58d19d4ad1c4b2925439a03e8e0be52.idella4@gentoo \
--to=idella4@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