From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/ncmpc/
Date: Sat, 6 Aug 2016 11:33:23 +0000 (UTC) [thread overview]
Message-ID: <1470483127.38ccd8db83092af7c6230f512aa03353d7ce4642.pacho@gentoo> (raw)
commit: 38ccd8db83092af7c6230f512aa03353d7ce4642
Author: Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 6 11:20:55 2016 +0000
Commit: Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Sat Aug 6 11:32:07 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=38ccd8db
media-sound/ncmpc: Cleanup per bug #177996
Package-Manager: portage-2.3.0
media-sound/ncmpc/metadata.xml | 4 ----
1 file changed, 4 deletions(-)
diff --git a/media-sound/ncmpc/metadata.xml b/media-sound/ncmpc/metadata.xml
index 9be901d..a9281ab 100644
--- a/media-sound/ncmpc/metadata.xml
+++ b/media-sound/ncmpc/metadata.xml
@@ -1,10 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person">
- <email>angelos@gentoo.org</email>
- <name>Christoph Mende</name>
- </maintainer>
<maintainer type="project">
<email>sound@gentoo.org</email>
<name>Gentoo Sound project</name>
next reply other threads:[~2016-08-06 11:33 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 11:33 Pacho Ramos [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-25 6:44 [gentoo-commits] repo/gentoo:master commit in: media-sound/ncmpc/ Miroslav Šulc
2024-09-24 7:51 Miroslav Šulc
2024-09-14 9:34 Miroslav Šulc
2023-09-24 20:18 Miroslav Šulc
2023-09-04 12:31 Sam James
2023-09-04 12:31 Sam James
2023-09-04 12:31 Sam James
2023-08-05 7:29 Miroslav Šulc
2023-05-10 5:13 Miroslav Šulc
2023-05-09 17:46 Sam James
2023-05-08 12:24 Arthur Zamarin
2023-05-08 12:24 Arthur Zamarin
2023-05-08 7:40 Sam James
2023-05-08 7:40 Sam James
2023-04-07 8:26 Miroslav Šulc
2022-08-04 4:58 Miroslav Šulc
2022-08-04 0:13 Sam James
2022-08-03 7:51 Agostino Sarubbo
2022-08-03 7:50 Agostino Sarubbo
2022-08-03 7:49 Agostino Sarubbo
2022-07-02 4:06 Miroslav Šulc
2022-03-17 9:08 Miroslav Šulc
2022-03-15 9:39 Jakov Smolić
2022-03-15 9:38 Jakov Smolić
2022-03-15 7:40 Agostino Sarubbo
2022-02-10 19:58 Miroslav Šulc
2021-04-23 4:53 Miroslav Šulc
2021-04-22 23:01 Sam James
2021-04-22 20:15 Sam James
2021-04-22 12:18 Sam James
2021-04-22 2:59 Sam James
2020-09-27 20:21 James Le Cuirot
2020-03-20 21:53 Matt Turner
2019-06-14 15:01 Agostino Sarubbo
2019-06-14 9:18 Agostino Sarubbo
2019-06-13 15:15 Agostino Sarubbo
2019-06-13 14:58 Agostino Sarubbo
2019-05-13 0:18 Andreas Sturmlechner
2019-04-28 22:41 Pacho Ramos
2019-04-28 22:06 Thomas Deutschmann
2019-04-07 23:19 Aaron Bauman
2019-04-07 21:34 Sergei Trofimovich
2019-02-09 18:17 Andreas Sturmlechner
2019-02-09 18:17 Andreas Sturmlechner
2019-02-09 18:17 Andreas Sturmlechner
2019-02-09 18:17 Andreas Sturmlechner
2019-02-09 18:17 Andreas Sturmlechner
2019-02-09 18:17 Andreas Sturmlechner
2019-01-04 8:06 Tim Harder
2018-09-21 10:35 Mikle Kolyada
2018-09-21 10:35 Mikle Kolyada
2018-09-20 5:12 Jeroen Roovers
2018-09-19 11:01 Mikle Kolyada
2018-09-09 6:16 Mikle Kolyada
2018-09-08 20:10 Mikle Kolyada
2017-04-26 5:33 Tim Harder
2016-08-21 1:11 Tim Harder
2015-10-20 4:30 Jeroen Roovers
2015-09-20 11:33 Christoph Mende
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=1470483127.38ccd8db83092af7c6230f512aa03353d7ce4642.pacho@gentoo \
--to=pacho@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