From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/UUID-Tiny/
Date: Sun, 11 Feb 2018 10:36:46 +0000 (UTC) [thread overview]
Message-ID: <1518345312.6a5dd3b6d694ec0d42e78fa3ef19a7ad875ed8f5.mgorny@gentoo> (raw)
commit: 6a5dd3b6d694ec0d42e78fa3ef19a7ad875ed8f5
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 10:31:53 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:35:12 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6a5dd3b6
dev-perl/UUID-Tiny: 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.
dev-perl/UUID-Tiny/metadata.xml | 2 --
1 file changed, 2 deletions(-)
diff --git a/dev-perl/UUID-Tiny/metadata.xml b/dev-perl/UUID-Tiny/metadata.xml
index 6fe837cf7d9..68d880192b5 100644
--- a/dev-perl/UUID-Tiny/metadata.xml
+++ b/dev-perl/UUID-Tiny/metadata.xml
@@ -3,11 +3,9 @@
<pkgmetadata>
<maintainer type="person">
<email>c.affolter@purplehaze.ch</email>
- <description>Maintainer</description>
</maintainer>
<maintainer type="person">
<email>dev-zero@gentoo.org</email>
- <description>Proxy maintainer</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2018-02-11 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 10:36 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-02 15:49 [gentoo-commits] repo/gentoo:master commit in: dev-perl/UUID-Tiny/ Andreas K. Hüttel
2021-04-02 14:04 Sam James
2017-09-18 16:50 Kent Fredric
2017-09-10 20:48 Patrice Clement
2015-10-29 16:11 Ian Delaney
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=1518345312.6a5dd3b6d694ec0d42e78fa3ef19a7ad875ed8f5.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