From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/ustr/
Date: Sun, 11 Feb 2018 10:36:45 +0000 (UTC) [thread overview]
Message-ID: <1518345257.0e050884ef6b7b3f707b237ff2576e4c56c441a9.mgorny@gentoo> (raw)
commit: 0e050884ef6b7b3f707b237ff2576e4c56c441a9
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 10:31:17 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:34:17 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0e050884
dev-libs/ustr: 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-libs/ustr/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/dev-libs/ustr/metadata.xml b/dev-libs/ustr/metadata.xml
index 524aa433671..b4a7d9f661c 100644
--- a/dev-libs/ustr/metadata.xml
+++ b/dev-libs/ustr/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>Yamakuzure@gmx.net</email>
<name>Sven Eden</name>
- <description>Maintainer. Assign bugs to him</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2018-02-11 10:36 UTC|newest]
Thread overview: 14+ 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 --
2020-11-13 22:05 [gentoo-commits] repo/gentoo:master commit in: dev-libs/ustr/ Aaron Bauman
2020-11-13 21:31 Aaron Bauman
2020-11-13 21:31 Aaron Bauman
2020-11-13 21:31 Aaron Bauman
2020-11-13 21:31 Aaron Bauman
2020-08-24 17:45 Jonas Stein
2018-04-02 10:25 Jonas Stein
2018-04-02 10:25 Jonas Stein
2016-06-10 13:53 Agostino Sarubbo
2016-02-17 18:42 Mike Frysinger
2016-02-17 18:42 Mike Frysinger
2016-02-17 18:42 Mike Frysinger
2015-09-15 6:28 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=1518345257.0e050884ef6b7b3f707b237ff2576e4c56c441a9.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