public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/flacon/
Date: Mon, 27 Jun 2016 00:25:38 +0000 (UTC)	[thread overview]
Message-ID: <1466986992.83d6bea1250a5f87458687e6bb3e8d88a897ada5.gokturk@gentoo> (raw)

commit:     83d6bea1250a5f87458687e6bb3e8d88a897ada5
Author:     Ilya Tumaykin <itumaykin <AT> gmail <DOT> com>
AuthorDate: Sun Jun 26 17:10:25 2016 +0000
Commit:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Mon Jun 27 00:23:12 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83d6bea1

media-sound/flacon: cleanup maintainer list

Acked-By: Maxim Koltsov <maksbotan <AT> gentoo.org>

Package-Manager: portage-2.3.0

 media-sound/flacon/metadata.xml | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/media-sound/flacon/metadata.xml b/media-sound/flacon/metadata.xml
index d5583ec..a3a3ef9 100644
--- a/media-sound/flacon/metadata.xml
+++ b/media-sound/flacon/metadata.xml
@@ -4,11 +4,6 @@
 	<maintainer type="person">
 		<email>itumaykin+gentoo@gmail.com</email>
 		<name>Coacher</name>
-		<description>Proxied maintainer; set to assignee in all bugs</description>
-	</maintainer>
-	<maintainer type="person">
-		<email>maksbotan@gentoo.org</email>
-		<name>Maxim Koltsov</name>
 	</maintainer>
 	<maintainer type="project">
 		<email>proxy-maint@gentoo.org</email>


             reply	other threads:[~2016-06-27  0:25 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27  0:25 Göktürk Yüksek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-01 16:48 [gentoo-commits] repo/gentoo:master commit in: media-sound/flacon/ Andreas Sturmlechner
2025-01-01 10:18 Joonas Niilola
2025-01-01  4:30 Sam James
2024-12-28  0:38 Andreas Sturmlechner
2024-12-10 16:03 Andreas Sturmlechner
2024-12-10 15:56 Joonas Niilola
2024-11-22 16:01 Joonas Niilola
2024-11-10 13:03 Sam James
2023-09-30 10:25 Daniel Pielmeier
2023-05-30  6:07 Joonas Niilola
2023-05-30  6:07 Joonas Niilola
2023-03-20  6:42 Joonas Niilola
2023-03-20  6:42 Joonas Niilola
2023-02-26  7:04 Joonas Niilola
2023-02-26  7:04 Joonas Niilola
2022-11-18  8:18 Joonas Niilola
2022-10-06  5:25 Joonas Niilola
2022-10-06  5:25 Joonas Niilola
2022-08-04  7:25 Joonas Niilola
2022-07-20  4:11 Joonas Niilola
2022-07-20  4:11 Joonas Niilola
2022-07-05  8:22 Joonas Niilola
2022-07-05  8:22 Joonas Niilola
2022-01-20 14:30 Sam James
2022-01-20 14:30 Sam James
2020-03-15 22:34 Andreas Sturmlechner
2020-03-15 11:45 Agostino Sarubbo
2019-12-07 15:01 Andreas Sturmlechner
2018-07-28  8:53 Michał Górny
2018-06-25  9:53 Jason Zaman
2018-04-30 16:08 Patrice Clement
2018-02-23 19:48 Andreas Sturmlechner
2018-02-01  1:45 Andreas Sturmlechner
2018-01-02 18:29 Patrice Clement
2018-01-02 18:29 Patrice Clement
2017-08-16  7:32 Michał Górny
2017-08-16  7:32 Michał Górny
2017-07-04  7:25 Patrice Clement
2017-05-15  9:09 Michał Górny
2017-02-25  1:03 Michael Palimaka
2017-01-04  6:19 Göktürk Yüksek
2016-12-28 13:27 Patrice Clement
2016-12-28 13:27 Patrice Clement
2016-10-26 21:29 Patrice Clement
2016-06-28 14:03 Patrice Clement
2016-06-02  7:42 Patrice Clement
2016-06-02  7:42 Patrice Clement
2016-06-02  7:42 Patrice Clement
2016-06-02  7:42 Patrice Clement
2016-05-10  9:28 Ian Delaney
2016-05-10  9:28 Ian Delaney
2016-05-10  9:28 Ian Delaney
2016-04-23 13:18 Davide Pesavento
2016-03-15 15:27 Agostino Sarubbo
2016-03-05 11:39 Patrice Clement
2016-02-02 11:07 Patrice Clement
2016-01-31 14:43 Patrice Clement
2016-01-31 14:43 Patrice Clement
2016-01-31 14:43 Patrice Clement
2016-01-31 14:43 Patrice Clement
2016-01-31 14:43 Patrice Clement
2016-01-31 14:43 Patrice Clement
2016-01-06 18:06 Ian Delaney
2016-01-02 16:28 Agostino Sarubbo
2015-12-01  7:02 Ian Delaney
2015-11-26  2:07 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=1466986992.83d6bea1250a5f87458687e6bb3e8d88a897ada5.gokturk@gentoo \
    --to=gokturk@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