From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/antiword/
Date: Sun, 11 Feb 2018 10:25:04 +0000 (UTC) [thread overview]
Message-ID: <1518344695.adea517a48d6000f882802917e3c97b9ea376d3c.mgorny@gentoo> (raw)
commit: adea517a48d6000f882802917e3c97b9ea376d3c
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 10:21:26 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:24:55 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=adea517a
app-text/antiword: 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-text/antiword/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/app-text/antiword/metadata.xml b/app-text/antiword/metadata.xml
index cc6b77e7c64..30c6e6d53c5 100644
--- a/app-text/antiword/metadata.xml
+++ b/app-text/antiword/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>clabbe.montjoie@gmail.com</email>
<name>LABBE Corentin (Montjoie)</name>
- <description>Maintainer. Assign bugs to him</description>
</maintainer>
<maintainer type="person">
<email>grobian@gentoo.org</email>
next reply other threads:[~2018-02-11 10:25 UTC|newest]
Thread overview: 12+ 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-01-26 20:10 [gentoo-commits] repo/gentoo:master commit in: app-text/antiword/ Fabian Groffen
2022-02-27 23:17 Sam James
2022-02-01 7:35 Agostino Sarubbo
2022-01-30 8:05 Agostino Sarubbo
2022-01-30 8:04 Agostino Sarubbo
2022-01-30 8:03 Agostino Sarubbo
2022-01-30 8:02 Agostino Sarubbo
2021-12-22 13:20 Fabian Groffen
2020-12-27 14:01 Fabian Groffen
2018-06-26 22:22 Jonas Stein
2016-06-21 18:27 Markus Meier
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=1518344695.adea517a48d6000f882802917e3c97b9ea376d3c.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