public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Manuel Rüger" <mrueg@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/drone/
Date: Sat, 23 Nov 2019 10:35:21 +0000 (UTC)	[thread overview]
Message-ID: <1574505309.f44a52ee8b6cb6a5e7344d273d6a1daef9d0707e.mrueg@gentoo> (raw)

commit:     f44a52ee8b6cb6a5e7344d273d6a1daef9d0707e
Author:     Manuel Rüger <mrueg <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 23 10:35:09 2019 +0000
Commit:     Manuel Rüger <mrueg <AT> gentoo <DOT> org>
CommitDate: Sat Nov 23 10:35:09 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f44a52ee

dev-util/drone: Drop to maintainer-needed

Package-Manager: Portage-2.3.76, Repoman-2.3.16
Signed-off-by: Manuel Rüger <mrueg <AT> gentoo.org>

 dev-util/drone/metadata.xml | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/dev-util/drone/metadata.xml b/dev-util/drone/metadata.xml
index 5a7b39bbcff..e15bf13f44f 100644
--- a/dev-util/drone/metadata.xml
+++ b/dev-util/drone/metadata.xml
@@ -1,10 +1,7 @@
 <?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-needed -->
 	<upstream>
 		<remote-id type="github">drone/drone</remote-id>
 	</upstream>


             reply	other threads:[~2019-11-23 10:35 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23 10:35 Manuel Rüger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-11 19:10 [gentoo-commits] repo/gentoo:master commit in: dev-util/drone/ William Hubbs
2023-08-09 17:47 William Hubbs
2022-10-02 17:57 William Hubbs
2022-05-13 23:00 Conrad Kostecki
2022-03-23  6:27 William Hubbs
2019-12-04  3:23 William Hubbs
2019-11-23 10:35 Manuel Rüger
2019-02-22 13:28 Manuel Rüger
2018-11-16 10:28 Manuel Rüger
2018-11-11 15:24 Manuel Rüger
2018-10-28 16:32 Manuel Rüger
2018-07-27 13:52 Manuel Rüger
2018-04-10  1:15 Manuel Rüger
2018-03-30 13:58 Manuel Rüger
2018-03-19 22:24 Manuel Rüger
2018-01-26 13:41 Manuel Rüger
2018-01-26 13:41 Manuel Rüger
2017-12-05 10:42 Manuel Rüger
2017-11-21 14:58 Manuel Rüger
2017-11-21 14:58 Manuel Rüger
2017-10-04  9:09 Michał Górny
2017-10-02 13:07 Manuel Rüger
2017-09-22 12:10 Manuel Rüger
2017-09-22 12:10 Manuel Rüger
2017-09-13 13:24 Manuel Rüger
2017-09-13 11:10 Manuel Rüger
2017-09-12 12:18 Manuel Rüger
2017-08-01 21:43 Manuel Rüger
2017-08-01 21:43 Manuel Rüger
2017-07-26 13:24 Manuel Rüger
2017-07-21 12:22 Manuel Rüger
2017-06-26 21:25 Manuel Rüger
2017-06-23 11:41 Manuel Rüger
2017-06-23 11:31 Manuel Rüger
2017-06-12 12:14 Manuel Rüger
2017-06-12 12:13 Manuel Rüger
2017-06-08 11:44 Manuel Rüger
2017-05-22 11:15 Manuel Rüger
2017-05-19 12:45 Manuel Rüger
2017-05-15 12:08 Manuel Rüger
2017-05-12 14:44 Manuel Rüger
2017-05-12 11:58 Manuel Rüger
2017-05-12 11:58 Manuel Rüger
2017-05-09 11:47 Manuel Rüger
2017-05-08 11:43 Manuel Rüger
2017-05-04 11:22 Manuel Rüger
2017-05-04 11:22 Manuel Rüger
2017-05-02 12:23 Manuel Rüger
2017-04-25 12:00 Manuel Rüger
2017-04-25 12:00 Manuel Rüger
2017-04-15 17:11 Manuel Rüger
2017-03-16 18:49 Manuel Rüger
2017-03-16 18:49 Manuel Rüger
2017-03-16 17:07 Manuel Rüger
2017-03-16 17:07 Manuel Rüger
2017-03-13 14:32 Manuel Rüger
2017-03-13 14:32 Manuel Rüger
2017-02-27 13:16 Manuel Rüger
2017-02-19 20:13 Manuel Rüger
2017-02-19 20:09 Manuel Rüger
2017-02-13 10:26 Manuel Rüger
2017-01-20 13:48 Manuel Rüger
2017-01-20 12:45 Manuel Rüger
2017-01-13 12:45 Manuel Rüger
2016-12-15 14:38 Manuel Rüger
2016-12-15 14:38 Manuel Rüger
2016-12-07 11:34 Manuel Rüger
2016-12-07 11:34 Manuel Rüger
2016-11-24 16:11 Manuel Rüger
2016-11-17 22:12 Manuel Rüger
2016-11-17 19:46 Manuel Rüger
2016-11-17 19:40 Manuel Rüger

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=1574505309.f44a52ee8b6cb6a5e7344d273d6a1daef9d0707e.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