From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/serialtalk/
Date: Sun, 11 Feb 2018 10:53:24 +0000 (UTC) [thread overview]
Message-ID: <1518346328.a25817bbdbd76c50e3ee060e70bcec239e08f75e.mgorny@gentoo> (raw)
commit: a25817bbdbd76c50e3ee060e70bcec239e08f75e
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 10:47:04 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:52:08 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a25817bb
dev-util/serialtalk: 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-util/serialtalk/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/dev-util/serialtalk/metadata.xml b/dev-util/serialtalk/metadata.xml
index cdeb0f43892..0dd8b67910d 100644
--- a/dev-util/serialtalk/metadata.xml
+++ b/dev-util/serialtalk/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>o.freyermuth@googlemail.com</email>
<name>Oliver Freyermuth</name>
- <description>Proxy-maintainer, assign bugs</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2018-02-11 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 10:53 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-21 7:15 [gentoo-commits] repo/gentoo:master commit in: dev-util/serialtalk/ Joonas Niilola
2020-07-17 7:44 Agostino Sarubbo
2020-07-17 7:21 Agostino Sarubbo
2020-05-04 17:26 Joonas Niilola
2017-12-16 17:24 Tobias Klausmann
2016-05-25 8:15 Patrice Clement
2016-05-06 13:16 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=1518346328.a25817bbdbd76c50e3ee060e70bcec239e08f75e.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