From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-doc/gnucash-docs/
Date: Sun, 13 Oct 2019 12:14:31 +0000 (UTC) [thread overview]
Message-ID: <1570968787.ca8ebca5159f7070ec2f9cd5ba3be343f4814c8e.leio@gentoo> (raw)
commit: ca8ebca5159f7070ec2f9cd5ba3be343f4814c8e
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 13 12:13:07 2019 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sun Oct 13 12:13:07 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ca8ebca5
app-doc/gnucash-docs: drop gnome@ from maintainers
Seems to live its maintenance life without gnome@ being involved,
so just drop us from maintainers.
Package-Manager: Portage-2.3.69, Repoman-2.3.12
Signed-off-by: Mart Raudsepp <leio <AT> gentoo.org>
app-doc/gnucash-docs/metadata.xml | 4 ----
1 file changed, 4 deletions(-)
diff --git a/app-doc/gnucash-docs/metadata.xml b/app-doc/gnucash-docs/metadata.xml
index dc94f737b78..74c00ed4c98 100644
--- a/app-doc/gnucash-docs/metadata.xml
+++ b/app-doc/gnucash-docs/metadata.xml
@@ -5,10 +5,6 @@
<email>titanofold@gentoo.org</email>
<name>Aaron W. Swenson</name>
</maintainer>
- <maintainer type="project">
- <email>gnome@gentoo.org</email>
- <name>Gentoo GNOME Desktop</name>
- </maintainer>
<upstream>
<remote-id type="sourceforge">gnucash</remote-id>
</upstream>
next reply other threads:[~2019-10-13 12:14 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 12:14 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-27 9:44 [gentoo-commits] repo/gentoo:master commit in: app-doc/gnucash-docs/ Sam James
2024-12-26 2:54 Sam James
2024-12-26 2:54 Sam James
2024-07-20 4:38 Sam James
2024-05-28 18:19 Arthur Zamarin
2024-05-28 17:01 Sam James
2024-05-11 18:36 Aaron W. Swenson
2024-01-20 14:42 Aaron W. Swenson
2023-09-23 21:07 Aaron W. Swenson
2023-05-12 23:58 Sam James
2023-05-03 23:05 Sam James
2023-05-03 18:54 Arthur Zamarin
2023-01-04 21:00 Andreas Sturmlechner
2023-01-04 6:31 Arthur Zamarin
2023-01-04 6:17 Arthur Zamarin
2022-12-06 12:47 Sam James
2022-12-06 12:33 Sam James
2022-12-06 12:33 Sam James
2022-12-06 12:02 Sam James
2022-12-06 12:02 Sam James
2022-12-06 12:02 Sam James
2022-05-07 5:00 Sam James
2022-03-30 14:14 Yixun Lan
2021-12-09 6:39 Sam James
2021-12-08 23:00 Sam James
2021-11-18 14:38 Aaron W. Swenson
2021-05-05 9:47 Aaron W. Swenson
2021-03-09 18:54 Aaron W. Swenson
2021-03-08 10:26 Sam James
2021-03-08 10:25 Sam James
2020-12-30 11:38 Aaron W. Swenson
2020-12-30 11:38 Aaron W. Swenson
2020-11-20 20:10 Aaron W. Swenson
2020-11-11 18:51 Sam James
2020-09-28 1:40 Aaron W. Swenson
2020-08-29 13:21 Sam James
2020-07-27 3:01 Aaron W. Swenson
2020-07-21 12:09 Aaron W. Swenson
2020-05-21 11:14 Aaron W. Swenson
2020-05-12 6:31 Agostino Sarubbo
2020-03-28 21:46 Aaron W. Swenson
2019-11-27 8:16 Agostino Sarubbo
2019-11-26 12:52 Agostino Sarubbo
2019-10-13 11:40 Andreas Sturmlechner
2019-08-30 17:50 Michał Górny
2019-07-18 12:56 Aaron W. Swenson
2019-07-03 9:37 Aaron W. Swenson
2019-04-10 11:30 Aaron W. Swenson
2019-01-09 13:06 Aaron W. Swenson
2018-11-10 12:03 Mikle Kolyada
2018-10-07 10:19 Aaron Swenson
2018-10-06 21:52 Mikle Kolyada
2018-10-05 4:10 Thomas Deutschmann
2018-10-03 2:03 Aaron Swenson
2018-08-11 11:25 Aaron Swenson
2018-08-11 11:23 Aaron Swenson
2018-07-09 9:18 Aaron Swenson
2018-05-13 16:03 Aaron Swenson
2018-05-13 16:03 Aaron Swenson
2018-04-27 20:24 Aaron Swenson
2018-01-06 17:03 Aaron Swenson
2017-02-15 16:49 Mart Raudsepp
2017-01-10 20:14 Pacho Ramos
2017-01-10 20:14 Pacho Ramos
2016-01-30 12:23 Pacho Ramos
2016-01-30 12:23 Pacho Ramos
2015-10-17 11:53 Pacho Ramos
2015-10-17 11:53 Pacho Ramos
2015-09-05 17:57 Pacho Ramos
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=1570968787.ca8ebca5159f7070ec2f9cd5ba3be343f4814c8e.leio@gentoo \
--to=leio@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