From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-power/acpi/
Date: Sun, 11 Feb 2018 11:36:43 +0000 (UTC) [thread overview]
Message-ID: <1518348989.2109384fe78ebb2354cc746b20a6446453e3a23f.mgorny@gentoo> (raw)
commit: 2109384fe78ebb2354cc746b20a6446453e3a23f
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:20:54 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:36:29 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2109384f
sys-power/acpi: 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-power/acpi/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/sys-power/acpi/metadata.xml b/sys-power/acpi/metadata.xml
index a1fc90f12a3..97dee5e7b9e 100644
--- a/sys-power/acpi/metadata.xml
+++ b/sys-power/acpi/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>axelgenus@gmail.com</email>
<name>Alessandro Calorì</name>
- <description>Proxied maintainer; set to assignee in all bugs</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2018-02-11 11:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 11:36 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-20 9:59 [gentoo-commits] repo/gentoo:master commit in: sys-power/acpi/ Jakov Smolić
2021-10-20 9:59 Jakov Smolić
2019-03-09 8:54 Pacho Ramos
2019-02-07 13:17 Mikle Kolyada
2018-06-18 18:48 Jonas Stein
2018-06-04 19:25 Mart Raudsepp
2017-07-08 14:12 Patrice Clement
2015-12-19 19:07 Patrice Clement
2015-12-19 19:07 Patrice Clement
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=1518348989.2109384fe78ebb2354cc746b20a6446453e3a23f.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