public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/moreutils/
Date: Tue, 31 Mar 2020 08:39:24 +0000 (UTC)	[thread overview]
Message-ID: <1585643940.9354eea7ee10e08c2c7245580b0b409721dab560.juippis@gentoo> (raw)

commit:     9354eea7ee10e08c2c7245580b0b409721dab560
Author:     Sam James (sam_c) <sam <AT> cmpct <DOT> info>
AuthorDate: Mon Mar 30 02:01:24 2020 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Tue Mar 31 08:39:00 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9354eea7

sys-apps/moreutils: Become proxy maintainer

Signed-off-by: Sam James (sam_c) <sam <AT> cmpct.info>
Closes: https://github.com/gentoo/gentoo/pull/15166
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 sys-apps/moreutils/metadata.xml | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/sys-apps/moreutils/metadata.xml b/sys-apps/moreutils/metadata.xml
index 77a13c050fa..7780744d4f5 100644
--- a/sys-apps/moreutils/metadata.xml
+++ b/sys-apps/moreutils/metadata.xml
@@ -1,7 +1,14 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
-<!-- maintainer-needed -->
+	<maintainer type="person">
+		<email>sam@cmpct.info</email>
+		<name>Sam James</name>
+	</maintainer>
+	<maintainer type="project">
+		<email>proxy-maint@gentoo.org</email>
+		<name>Proxy Maintainers</name>
+	</maintainer>
 <use>
 	<flag name="perl">Install scripts written in Perl</flag>
 </use>


             reply	other threads:[~2020-03-31  8:39 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  8:39 Joonas Niilola [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-14  6:39 [gentoo-commits] repo/gentoo:master commit in: sys-apps/moreutils/ Sam James
2025-01-22  7:54 Sam James
2025-01-22  7:54 Sam James
2025-01-22  7:54 Sam James
2025-01-22  7:29 Sam James
2024-12-13 13:58 Sam James
2024-04-29 13:42 Sam James
2024-04-29 13:42 Sam James
2024-04-29  5:50 Sam James
2024-04-29  5:48 Sam James
2024-02-29  4:22 Sam James
2024-02-29  4:22 Sam James
2024-01-07 12:42 Arthur Zamarin
2024-01-07 12:42 Arthur Zamarin
2024-01-07  9:31 Sam James
2024-01-07  9:31 Sam James
2023-12-03  9:02 Sam James
2023-02-01  7:38 Sam James
2022-02-20  5:51 Sam James
2022-01-26  5:06 Sam James
2022-01-26  5:06 Sam James
2022-01-26  5:06 Sam James
2022-01-26  5:04 Sam James
2022-01-01  9:38 Sam James
2021-12-24  7:38 Sam James
2021-10-27  4:13 Sam James
2021-10-26  3:14 Sam James
2021-10-21 23:28 Sam James
2021-10-21 23:28 Sam James
2021-09-20  2:39 Sam James
2021-02-15  1:51 Sam James
2021-02-15  1:49 Sam James
2021-02-13 21:15 Sam James
2021-02-03 23:55 Thomas Deutschmann
2021-02-02 21:00 Sam James
2021-01-03 23:20 Sam James
2021-01-03 23:17 Sam James
2020-11-28  9:17 Sam James
2020-11-28  9:13 Sam James
2020-11-28  9:11 Sam James
2020-10-06 13:09 Sam James
2020-10-02 21:00 Sam James
2020-10-02 15:22 Sergei Trofimovich
2020-09-02 23:33 Sam James
2020-07-08 20:50 Sam James
2020-07-08 20:50 Sam James
2020-06-06 18:01 Michał Górny
2020-05-13 21:07 Mart Raudsepp
2020-01-16 12:32 Tim Harder
2019-12-19 18:35 Sergei Trofimovich
2019-12-15 13:53 Agostino Sarubbo
2019-12-15 12:44 Agostino Sarubbo
2019-11-17 22:10 Tim Harder
2019-04-03  4:46 Tim Harder
2019-01-04  6:40 Tim Harder
2018-02-03  9:15 Tim Harder
2018-02-03  9:15 Tim Harder
2017-09-16 21:43 Sergei Trofimovich
2017-09-03 17:23 Tim Harder
2017-08-31 15:46 Tim Harder
2017-04-27  7:35 Tim Harder
2017-04-27  7:22 Tim Harder
2017-02-05 13:19 Jeroen Roovers
2017-01-04 19:51 Tim Harder
2017-01-04 19:42 Tim Harder
2016-08-19 10:07 Pacho Ramos
2016-08-19  3:26 Tim Harder
2016-07-21  2:06 Tim Harder
2016-03-12  7:16 Tim Harder
2015-08-25  2:47 Tim Harder

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=1585643940.9354eea7ee10e08c2c7245580b0b409721dab560.juippis@gentoo \
    --to=juippis@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