From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/biosdisk/
Date: Sun, 11 Feb 2018 11:12:23 +0000 (UTC) [thread overview]
Message-ID: <1518347303.d9a6b03b157f6760c5a80e67c2bd7831e6759d22.mgorny@gentoo> (raw)
commit: d9a6b03b157f6760c5a80e67c2bd7831e6759d22
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:08:23 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:08:23 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d9a6b03b
sys-apps/biosdisk: 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.
sys-apps/biosdisk/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/sys-apps/biosdisk/metadata.xml b/sys-apps/biosdisk/metadata.xml
index 2e67e478e9f..abf4a100a13 100644
--- a/sys-apps/biosdisk/metadata.xml
+++ b/sys-apps/biosdisk/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>mattsch@gmail.com</email>
<name>Matthew Schultz</name>
- <description>Assign bugs to him</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2018-02-11 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 11:12 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-03 6:17 [gentoo-commits] repo/gentoo:master commit in: sys-apps/biosdisk/ Sam James
2020-08-03 5:31 Robin H. Johnson
2020-06-24 20:29 Conrad Kostecki
2020-06-24 20:29 Conrad Kostecki
2018-03-13 19:16 Michał Górny
2018-03-13 19:16 Michał Górny
2017-02-04 15:40 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=1518347303.d9a6b03b157f6760c5a80e67c2bd7831e6759d22.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