From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-cdr/cdrdao/
Date: Sun, 11 Feb 2018 10:01:23 +0000 (UTC) [thread overview]
Message-ID: <1518343271.8d732322feb6de09f5120f82da9c99c022b14d7f.mgorny@gentoo> (raw)
commit: 8d732322feb6de09f5120f82da9c99c022b14d7f
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 09:55:00 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:01:11 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8d732322
app-cdr/cdrdao: 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.
app-cdr/cdrdao/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/app-cdr/cdrdao/metadata.xml b/app-cdr/cdrdao/metadata.xml
index f71e7172b1d..0981f4cab9a 100644
--- a/app-cdr/cdrdao/metadata.xml
+++ b/app-cdr/cdrdao/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>brendan@horan.hk</email>
<name>Brendan Horan</name>
- <description>Proxy maintainer - make assignee on bugs</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2018-02-11 10:01 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 10:01 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-16 11:21 [gentoo-commits] repo/gentoo:master commit in: app-cdr/cdrdao/ Sam James
2023-12-16 10:59 Arthur Zamarin
2023-05-27 9:43 Sam James
2023-05-27 9:43 Sam James
2023-05-23 0:10 Sam James
2023-05-18 19:42 Sam James
2023-05-18 19:42 Sam James
2023-05-18 19:17 Arthur Zamarin
2023-03-04 10:15 Arthur Zamarin
2023-03-04 6:34 Arthur Zamarin
2023-03-03 18:50 Arthur Zamarin
2023-03-03 17:25 Arthur Zamarin
2022-12-04 15:59 WANG Xuerui
2022-07-28 8:28 Sam James
2022-07-28 8:28 Sam James
2022-06-21 7:38 Agostino Sarubbo
2022-06-21 7:37 Agostino Sarubbo
2022-06-21 7:36 Agostino Sarubbo
2022-06-20 18:49 Arthur Zamarin
2022-06-20 6:04 Joonas Niilola
2022-06-20 6:04 Joonas Niilola
2022-02-15 7:00 Joonas Niilola
2021-09-24 1:37 Yixun Lan
2020-12-18 9:00 Michał Górny
2018-11-28 12:15 Tobias Klausmann
2018-11-06 23:56 Sergei Trofimovich
2018-11-06 21:31 Mikle Kolyada
2018-11-05 7:51 Sergei Trofimovich
2018-11-05 7:51 Sergei Trofimovich
2018-11-01 19:07 Sergei Trofimovich
2018-10-31 23:35 Sergei Trofimovich
2018-10-31 1:04 Thomas Deutschmann
2018-04-15 18:48 Patrice Clement
2018-02-28 20:11 Andreas Sturmlechner
2018-02-27 21:56 Sergei Trofimovich
2017-12-10 0:32 Sergei Trofimovich
2017-12-02 23:51 Sergei Trofimovich
2017-11-30 20:19 Tobias Klausmann
2017-11-29 20:28 Sergei Trofimovich
2017-05-22 9:25 Agostino Sarubbo
2017-05-21 8:09 Agostino Sarubbo
2017-02-11 12:50 Pacho Ramos
2016-05-03 20:56 Markus Meier
2016-04-13 0:59 Sam Jorna
2016-04-07 10:17 Jeroen Roovers
2016-03-06 20:52 Mikle Kolyada
2016-02-21 23:44 Pacho Ramos
2016-01-11 2:33 Mike Frysinger
2015-12-23 10:59 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=1518343271.8d732322feb6de09f5120f82da9c99c022b14d7f.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