public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jonas Stein" <jstein@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-db/mydumper/
Date: Sun,  1 Oct 2017 10:30:10 +0000 (UTC)	[thread overview]
Message-ID: <1506853788.b42fc56f0913e4a6cb001bba07f12b0ce5304f3a.jstein@gentoo> (raw)

commit:     b42fc56f0913e4a6cb001bba07f12b0ce5304f3a
Author:     Jonas Stein <jstein <AT> gentoo <DOT> org>
AuthorDate: Sun Oct  1 10:29:48 2017 +0000
Commit:     Jonas Stein <jstein <AT> gentoo <DOT> org>
CommitDate: Sun Oct  1 10:29:48 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b42fc56f

dev-db/mydumper: Drop inactive proxied maintainer

jstein and gokturk had mailcontact with the proxied maintainer;
he does not maintain his packages anymore.

Package-Manager: Portage-2.3.10, Repoman-2.3.3

 dev-db/mydumper/metadata.xml | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/dev-db/mydumper/metadata.xml b/dev-db/mydumper/metadata.xml
index 1686e37bb94..d950a2af5b5 100644
--- a/dev-db/mydumper/metadata.xml
+++ b/dev-db/mydumper/metadata.xml
@@ -1,14 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
-	<maintainer type="person">
-		<email>pavel.stratil-jun@fenix.cz</email>
-		<description>Proxied co-maintainer, assign bugs to him</description>
-	</maintainer>
-	<maintainer type="project">
-		<email>proxy-maint@gentoo.org</email>
-		<name>Proxy Maintainers</name>
-	</maintainer>
+<!-- maintainer-needed -->
 	<upstream>
 		<remote-id type="launchpad">mydumper</remote-id>
 	</upstream>


             reply	other threads:[~2017-10-01 10:30 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01 10:30 Jonas Stein [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-11 14:24 [gentoo-commits] repo/gentoo:master commit in: dev-db/mydumper/ Sam James
2024-03-07 16:33 Petr Vaněk
2024-03-07 16:33 Petr Vaněk
2024-03-07 16:33 Petr Vaněk
2023-11-02 10:25 Sam James
2023-10-21  8:43 Joonas Niilola
2023-09-01 17:15 Arthur Zamarin
2023-09-01 17:15 Arthur Zamarin
2023-08-19  4:26 Sam James
2023-07-14  6:50 Joonas Niilola
2023-07-14  6:50 Joonas Niilola
2023-06-23 20:16 Sam James
2023-04-26  4:03 Sam James
2023-04-17 11:56 Sam James
2023-02-15  5:53 Sam James
2022-11-10 16:15 Joonas Niilola
2022-10-25 17:55 Sam James
2022-08-04  6:37 Joonas Niilola
2022-08-04  6:37 Joonas Niilola
2022-05-13 20:04 Sam James
2022-04-29 12:20 Joonas Niilola
2022-02-06 19:47 Ionen Wolkens
2022-01-07  5:14 Sam James
2022-01-07  5:14 Sam James
2021-12-09 16:22 Agostino Sarubbo
2021-10-15 10:22 Joonas Niilola
2021-10-15 10:22 Joonas Niilola
2021-10-15 10:22 Joonas Niilola
2021-09-29 14:07 Sam James
2021-08-08 19:21 Ionen Wolkens
2021-08-08 19:21 Ionen Wolkens
2021-05-23 22:28 Agostino Sarubbo
2021-04-16  6:26 Joonas Niilola
2021-02-05 10:40 Sam James
2021-02-04 22:27 Thomas Deutschmann
2021-02-04 22:27 Thomas Deutschmann
2019-01-07 17:00 Lars Wendler
2018-10-02  9:33 Thomas Deutschmann
2018-05-24 10:23 Amy Liffey
2017-10-08 12:29 Amy Liffey
2017-03-23 20:53 David Seifert

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=1506853788.b42fc56f0913e4a6cb001bba07f12b0ce5304f3a.jstein@gentoo \
    --to=jstein@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