From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-wm/evilwm/
Date: Sun, 11 Feb 2018 11:36:44 +0000 (UTC) [thread overview]
Message-ID: <1518348998.ae8c86b1e93916c4d194747a30006b8bbfc6d507.mgorny@gentoo> (raw)
commit: ae8c86b1e93916c4d194747a30006b8bbfc6d507
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:21:42 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:36:38 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ae8c86b1
x11-wm/evilwm: 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.
x11-wm/evilwm/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/x11-wm/evilwm/metadata.xml b/x11-wm/evilwm/metadata.xml
index e91a07af8e6..623c55d7f8c 100644
--- a/x11-wm/evilwm/metadata.xml
+++ b/x11-wm/evilwm/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>jaco@uls.co.za</email>
<name>Jaco Kroon</name>
- <description>Proxy-Maintainer. Assign bugs to him</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2018-02-11 11:37 UTC|newest]
Thread overview: 20+ 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 --
2024-10-04 8:13 [gentoo-commits] repo/gentoo:master commit in: x11-wm/evilwm/ Sam James
2024-08-01 16:51 Andreas Sturmlechner
2024-08-01 16:51 Andreas Sturmlechner
2023-12-19 17:01 Arthur Zamarin
2023-12-18 7:10 Joonas Niilola
2023-12-18 1:09 Sam James
2023-05-27 7:49 Joonas Niilola
2023-05-27 7:49 Joonas Niilola
2022-08-29 8:06 Andreas Sturmlechner
2021-09-26 17:52 Sam James
2021-09-26 17:52 Sam James
2021-09-26 7:28 Agostino Sarubbo
2021-09-03 5:33 Joonas Niilola
2018-01-04 11:47 Mikle Kolyada
2018-01-04 11:45 Mikle Kolyada
2017-12-28 10:10 David Seifert
2017-12-26 18:56 Amy Liffey
2017-01-15 11:37 Manuel Rüger
2015-09-04 13:36 Tony Vroon
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=1518348998.ae8c86b1e93916c4d194747a30006b8bbfc6d507.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