public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-news/rssguard/
Date: Tue, 20 Jun 2017 12:37:56 +0000 (UTC)	[thread overview]
Message-ID: <1497962267.2752a4c3fad0d256637fb82c9b36b78556b0c3c3.pacho@gentoo> (raw)

commit:     2752a4c3fad0d256637fb82c9b36b78556b0c3c3
Author:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 20 12:11:28 2017 +0000
Commit:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Tue Jun 20 12:37:47 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2752a4c3

net-news/rssguard: Cleanup metadata due to retirement

Package-Manager: Portage-2.3.6, Repoman-2.3.2

 net-news/rssguard/metadata.xml | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/net-news/rssguard/metadata.xml b/net-news/rssguard/metadata.xml
index 12ad4e9c7ac..10ef77a1959 100644
--- a/net-news/rssguard/metadata.xml
+++ b/net-news/rssguard/metadata.xml
@@ -1,9 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
-	<maintainer type="person">
-		<email>yngwin@gentoo.org</email>
-	</maintainer>
 	<upstream>
 		<remote-id type="github">martinrotter/rssguard</remote-id>
 	</upstream>


             reply	other threads:[~2017-06-20 12:38 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 12:37 Pacho Ramos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-02  7:06 [gentoo-commits] repo/gentoo:master commit in: net-news/rssguard/ Michał Górny
2025-01-05  2:55 Michał Górny
2024-12-20  8:23 Michał Górny
2024-10-12 15:47 Michał Górny
2024-10-12 14:57 Sam James
2024-10-07 18:48 Michał Górny
2024-09-27  6:32 Michał Górny
2024-08-10 11:16 Michał Górny
2024-08-10 10:28 Michał Górny
2024-07-26 15:28 Michał Górny
2024-06-15  8:42 Michał Górny
2024-06-15  8:40 Arthur Zamarin
2024-05-31 15:21 Michał Górny
2024-05-31 15:21 Michał Górny
2024-05-30  3:31 Michał Górny
2024-05-15  2:08 Michał Górny
2024-03-30 14:27 Michał Górny
2024-03-30 14:25 Michał Górny
2024-03-15 13:15 Michał Górny
2024-01-18 18:46 Michał Górny
2024-01-18 17:37 Arthur Zamarin
2023-12-15 16:59 Michał Górny
2023-12-09  6:53 Michał Górny
2023-12-07 17:24 Michał Górny
2023-12-02 11:12 Michał Górny
2023-12-02 10:35 Arthur Zamarin
2023-11-14 20:06 Michał Górny
2023-11-13 17:41 Michał Górny
2023-11-12  3:59 Michał Górny
2023-11-11 22:41 Sam James
2023-11-02 14:28 Michał Górny
2023-11-01 16:05 Michał Górny
2023-10-05 14:59 Michał Górny
2023-08-25  9:49 Michał Górny
2023-08-20 10:57 Michał Górny
2023-08-20 10:29 Sam James
2023-07-10 19:26 Arthur Zamarin
2023-06-28  5:06 Michał Górny
2023-05-13  9:04 Michał Górny
2023-05-13  8:40 Arthur Zamarin
2023-05-13  8:35 Michał Górny
2023-05-08  7:44 Joonas Niilola
2023-05-08  7:44 Joonas Niilola
2023-04-04 16:43 Arthur Zamarin
2023-02-09 15:53 Joonas Niilola
2023-02-09 15:53 Joonas Niilola
2023-01-13 13:47 Joonas Niilola
2023-01-13 13:47 Joonas Niilola
2022-10-03 18:34 Ionen Wolkens
2022-06-09  0:57 Ionen Wolkens
2022-03-24  7:28 Ionen Wolkens
2022-01-19 16:28 Joonas Niilola
2021-10-30  6:24 Joonas Niilola
2021-09-28 13:26 Joonas Niilola
2021-09-09 11:30 Joonas Niilola
2021-09-09 11:30 Joonas Niilola
2021-07-07 13:41 Joonas Niilola
2020-12-17 17:33 Sam James
2020-12-16  1:44 Sam James
2020-12-15  3:25 Sam James
2020-12-15  3:25 Sam James
2020-01-18 17:16 Andreas Sturmlechner
2020-01-05 20:08 Jeroen Roovers
2020-01-05 17:00 Andreas Sturmlechner
2020-01-05 17:00 Andreas Sturmlechner
2018-10-20 12:17 Pacho Ramos
2018-10-20 12:17 Pacho Ramos
2018-07-18 21:11 Jonas Stein
2017-11-29 23:19 Andreas Sturmlechner
2017-11-29 23:19 Andreas Sturmlechner
2017-08-13 13:23 Patrice Clement
2017-08-13 13:23 Patrice Clement
2016-11-24 10:54 Michael Palimaka
2015-10-01 14:21 Michael Palimaka

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=1497962267.2752a4c3fad0d256637fb82c9b36b78556b0c3c3.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