From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-office/grisbi/
Date: Sun, 11 Feb 2018 10:25:03 +0000 (UTC) [thread overview]
Message-ID: <1518344689.4d4e72e5aaf476e7b54fc6e7476d1629a9ecaf6b.mgorny@gentoo> (raw)
commit: 4d4e72e5aaf476e7b54fc6e7476d1629a9ecaf6b
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 10:20:53 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:24:49 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4d4e72e5
app-office/grisbi: Remove useless maintainer <description/>
Remove useless/redundant maintainer <description/>. It does not benefit
bug wrangling, and only wastes developer's time on reading it. Few tips:
- assignee/CC is implied by ordering, there is no reason to repeat it,
- we know that maintainer is maintainer (la la la la la),
- most of adjectives for maintainer are of no value and/or are obvious.
app-office/grisbi/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/app-office/grisbi/metadata.xml b/app-office/grisbi/metadata.xml
index e8c4a349ec5..105a80c6723 100644
--- a/app-office/grisbi/metadata.xml
+++ b/app-office/grisbi/metadata.xml
@@ -7,7 +7,6 @@
<maintainer type="person">
<email>casta@xwing.info</email>
<name>Guillaume Castagnino</name>
- <description>Third party maintainer</description>
</maintainer>
<maintainer type="project">
<email>gnome@gentoo.org</email>
next reply other threads:[~2018-02-11 10:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 10:25 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-26 8:11 [gentoo-commits] repo/gentoo:master commit in: app-office/grisbi/ Joonas Niilola
2024-07-26 8:11 Joonas Niilola
2024-01-28 12:24 Pacho Ramos
2023-12-18 10:19 Pacho Ramos
2023-11-24 13:16 Pacho Ramos
2022-09-27 21:22 Sam James
2022-03-19 17:10 David Seifert
2021-12-19 21:21 Jakov Smolić
2021-12-17 8:38 Agostino Sarubbo
2021-09-02 12:54 Joonas Niilola
2021-09-02 12:54 Joonas Niilola
2021-09-02 12:54 Joonas Niilola
2021-07-04 18:24 Matt Turner
2021-05-04 1:01 Matt Turner
2021-05-02 12:42 Mikle Kolyada
2021-01-03 22:56 Sam James
2020-01-28 9:39 Mart Raudsepp
2019-10-08 21:44 Rémi Cardona
2019-03-31 22:30 Rémi Cardona
2018-07-11 8:50 Tony Vroon
2018-04-29 0:08 Mart Raudsepp
2018-04-26 22:32 Aaron Bauman
2018-04-26 17:15 Thomas Deutschmann
2018-01-18 19:54 Amy Liffey
2016-11-03 11:19 Pacho Ramos
2016-11-03 11:19 Pacho Ramos
2016-11-03 11:19 Pacho Ramos
2016-09-18 11:01 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=1518344689.4d4e72e5aaf476e7b54fc6e7476d1629a9ecaf6b.mgorny@gentoo \
--to=mgorny@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