public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel Campbell" <zlg@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/astyle/
Date: Tue, 12 Dec 2017 21:46:51 +0000 (UTC)	[thread overview]
Message-ID: <1513115160.30f416de2cac5c79c18819b27963dd1aadcf9f08.zlg@gentoo> (raw)

commit:     30f416de2cac5c79c18819b27963dd1aadcf9f08
Author:     Daniel Campbell <zlg <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 12 21:33:23 2017 +0000
Commit:     Daniel Campbell <zlg <AT> gentoo <DOT> org>
CommitDate: Tue Dec 12 21:46:00 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=30f416de

dev-util/astyle: Remove self as maintainer

Package-Manager: Portage-2.3.16, Repoman-2.3.6

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

diff --git a/dev-util/astyle/metadata.xml b/dev-util/astyle/metadata.xml
index 284e178263a..20b3820d15c 100644
--- a/dev-util/astyle/metadata.xml
+++ b/dev-util/astyle/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>zlg@gentoo.org</email>
-		<name>Daniel Campbell</name>
-	</maintainer>
+	<!-- maintainer-needed -->
 	<longdescription>
 		astyle is a code formatter for C, C++, and Java source code, with many
 		granular formatting options to assist in enforcing code formatting


             reply	other threads:[~2017-12-12 21:46 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 21:46 Daniel Campbell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-10  2:21 [gentoo-commits] repo/gentoo:master commit in: dev-util/astyle/ Sam James
2025-03-10  2:21 Sam James
2024-11-09 13:24 Arthur Zamarin
2024-11-09 10:06 Arthur Zamarin
2024-11-09  2:14 Sam James
2024-11-09  2:14 Sam James
2024-09-11 15:31 Alfredo Tupone
2024-08-03  6:19 Joonas Niilola
2024-08-03  6:17 Joonas Niilola
2024-08-02 16:19 Sam James
2024-08-02 16:19 Sam James
2024-08-02 16:19 Sam James
2024-08-02 13:45 Viorel Munteanu
2024-08-02 13:45 Viorel Munteanu
2024-08-02 13:45 Viorel Munteanu
2023-10-20  0:51 Sam James
2023-09-24  4:39 Sam James
2023-09-24  4:39 Sam James
2023-08-30  7:48 Sam James
2023-08-30  7:48 Sam James
2023-06-19 21:28 Sam James
2023-01-23  2:30 Matthias Maier
2023-01-23  2:30 Matthias Maier
2021-02-05 12:29 Sam James
2021-02-02 21:02 Sam James
2020-02-26 18:25 Andreas Sturmlechner
2018-10-24  7:34 Mikle Kolyada
2018-10-17 12:07 Thomas Deutschmann
2018-08-08 10:03 Guilherme Amadio
2018-05-29  0:41 Matthias Maier
2018-05-28 22:17 Matthias Maier
2018-05-28 22:17 Matthias Maier
2018-05-28 22:17 Matthias Maier
2018-05-28 22:17 Matthias Maier
2018-03-06 17:44 Amy Liffey
2018-03-06 16:08 Amy Liffey
2018-02-07  0:54 Matthias Maier
2017-12-19  6:50 Matthias Maier
2017-08-29 23:16 Thomas Deutschmann
2017-07-31 12:56 Tobias Klausmann
2017-07-30 10:57 Sergei Trofimovich
2017-06-23 19:39 Daniel Campbell
2017-06-18  6:23 Daniel Campbell
2017-06-18  6:23 Daniel Campbell
2017-01-02 14:36 Daniel Campbell
2016-03-18 19:11 Michał Górny
2016-03-06 22:20 Daniel Campbell
2016-01-26  0:50 Daniel Campbell
2015-08-26 11:00 Agostino Sarubbo

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=1513115160.30f416de2cac5c79c18819b27963dd1aadcf9f08.zlg@gentoo \
    --to=zlg@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