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: app-misc/gramps/
Date: Sat, 28 May 2016 09:32:04 +0000 (UTC)	[thread overview]
Message-ID: <1464427865.86fdd7eadd271c8f24f1809941fa9c8920f6e68e.pacho@gentoo> (raw)

commit:     86fdd7eadd271c8f24f1809941fa9c8920f6e68e
Author:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Sat May 28 09:26:08 2016 +0000
Commit:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Sat May 28 09:31:05 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=86fdd7ea

app-misc/gramps: Cleanup due to #148577

Package-Manager: portage-2.3.0_rc1

 app-misc/gramps/metadata.xml | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/app-misc/gramps/metadata.xml b/app-misc/gramps/metadata.xml
index 7de1449..4c7b0b7 100644
--- a/app-misc/gramps/metadata.xml
+++ b/app-misc/gramps/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>fauli@gentoo.org</email>
-		<name>Christian Faulhammer</name>
-	</maintainer>
 	<longdescription lang="en">
 GRAMPS helps you track your family tree. It allows you to store, edit,
 and research genealogical data. GRAMPS attempts to provide all of the


             reply	other threads:[~2016-05-28  9:32 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-28  9:32 Pacho Ramos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-07 19:48 [gentoo-commits] repo/gentoo:master commit in: app-misc/gramps/ Austin English
2016-09-23  6:57 Marek Szuba
2016-09-23  7:37 Marek Szuba
2016-10-20 23:55 David Seifert
2016-11-13 15:02 Marek Szuba
2016-11-16  9:33 Marek Szuba
2016-12-29 11:36 Agostino Sarubbo
2016-12-29 11:41 Agostino Sarubbo
2017-01-15 19:54 Göktürk Yüksek
2017-04-28  4:03 Michael Orlitzky
2017-04-28  4:03 Michael Orlitzky
2017-06-02 20:02 Agostino Sarubbo
2017-06-04 10:42 Agostino Sarubbo
2018-03-24 19:58 Michał Górny
2018-03-24 19:58 Michał Górny
2018-03-24 19:58 Michał Górny
2018-03-24 19:58 Michał Górny
2018-06-27 17:20 Pacho Ramos
2018-06-30 10:04 Pacho Ramos
2018-07-01  9:45 Mikle Kolyada
2018-10-11 14:37 Marek Szuba
2018-10-11 14:37 Marek Szuba
2019-01-09 14:38 Marek Szuba
2019-07-15 11:46 Marek Szuba
2019-07-15 14:17 Agostino Sarubbo
2019-07-18  7:26 Agostino Sarubbo
2019-08-09 15:11 Marek Szuba
2019-10-29 15:54 Marek Szuba
2020-01-13 14:49 Marek Szuba
2020-01-13 14:49 Marek Szuba
2020-01-13 14:49 Marek Szuba
2020-02-12 14:20 Agostino Sarubbo
2020-02-12 18:22 Agostino Sarubbo
2020-03-04 10:00 Marek Szuba
2020-04-21 12:31 Marek Szuba
2020-04-21 22:21 Marek Szuba
2020-04-22 23:48 Marek Szuba
2020-07-14 20:56 Marek Szuba
2020-07-29 11:33 Marek Szuba
2020-08-24 17:19 Marek Szuba
2020-11-13 14:30 Sam James
2021-02-15 12:39 Marek Szuba
2021-04-29  1:52 Sam James
2021-05-15 14:22 Marek Szuba
2021-07-28 18:41 Marek Szuba
2021-09-11  6:02 Sam James
2021-09-11  6:42 Agostino Sarubbo
2021-09-13 17:11 Marek Szuba
2022-02-07 19:39 Marek Szuba
2022-04-10  9:05 Agostino Sarubbo
2022-04-11  6:50 Agostino Sarubbo
2022-04-11 11:16 Marek Szuba
2022-05-18 23:18 Marek Szuba
2023-02-27  0:23 Marek Szuba
2023-05-01 13:43 Sam James
2023-07-08 23:39 Marek Szuba
2023-07-10 23:04 Marek Szuba
2023-08-22 11:16 Sam James
2023-08-22 21:35 Marek Szuba
2023-09-07  8:38 Marek Szuba
2023-09-07  8:38 Marek Szuba
2023-09-08  9:56 Marek Szuba
2023-10-23 23:08 Sam James
2023-10-24 23:16 Marek Szuba
2024-04-08 13:15 Marek Szuba
2024-05-28 13:19 Sam James
2024-09-05 13:27 Petr Vaněk
2024-09-06 10:12 Petr Vaněk
2024-10-06  8:26 Sam James

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=1464427865.86fdd7eadd271c8f24f1809941fa9c8920f6e68e.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