From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/liblognorm/
Date: Sun, 11 Feb 2018 10:36:45 +0000 (UTC) [thread overview]
Message-ID: <1518345246.49ea852de7cbd4be09009da4b5110603a4d6729c.mgorny@gentoo> (raw)
commit: 49ea852de7cbd4be09009da4b5110603a4d6729c
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 10:31:11 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:34:06 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=49ea852d
dev-libs/liblognorm: 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-libs/liblognorm/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/dev-libs/liblognorm/metadata.xml b/dev-libs/liblognorm/metadata.xml
index a2706918f5c..a1c7f71484f 100644
--- a/dev-libs/liblognorm/metadata.xml
+++ b/dev-libs/liblognorm/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>whissi@gentoo.org</email>
<name>Thomas Deutschmann</name>
- <description>Primary maintainer</description>
</maintainer>
<maintainer type="person">
<email>maksbotan@gentoo.org</email>
next reply other threads:[~2018-02-11 10:36 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 10:36 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-04 18:21 [gentoo-commits] repo/gentoo:master commit in: dev-libs/liblognorm/ Arthur Zamarin
2022-08-28 5:55 Jakov Smolić
2022-08-23 18:10 Arthur Zamarin
2022-08-05 9:31 Arthur Zamarin
2021-05-16 0:03 Sam James
2019-12-31 3:17 Thomas Deutschmann
2019-04-20 1:29 Aaron Bauman
2019-01-03 19:12 Mikle Kolyada
2018-12-28 12:17 Sergei Trofimovich
2018-12-20 1:30 Thomas Deutschmann
2018-12-19 20:19 Mikle Kolyada
2018-11-07 21:18 Thomas Deutschmann
2018-08-03 1:19 Thomas Deutschmann
2018-07-23 19:00 Sergei Trofimovich
2018-07-22 15:18 Mikle Kolyada
2018-07-09 0:37 Mikle Kolyada
2018-07-04 3:17 Thomas Deutschmann
2018-05-21 19:02 Thomas Deutschmann
2018-04-26 22:00 Thomas Deutschmann
2018-03-28 5:05 Markus Meier
2018-02-10 0:32 Thomas Deutschmann
2018-01-28 16:08 Mikle Kolyada
2017-10-04 23:15 Thomas Deutschmann
2017-06-19 10:09 Alexis Ballier
2017-05-22 17:27 Thomas Deutschmann
2017-05-22 13:31 Agostino Sarubbo
2017-05-19 7:50 Jeroen Roovers
2017-03-29 15:24 Thomas Deutschmann
2017-02-21 20:39 Markus Meier
2017-01-20 5:06 Jeroen Roovers
2017-01-11 11:13 Aaron Bauman
2016-12-23 15:09 Markus Meier
2016-11-27 21:08 Thomas Deutschmann
2016-11-17 22:00 Thomas Deutschmann
2016-09-25 19:55 Jeroen Roovers
2016-08-28 18:48 Thomas Deutschmann
2016-08-24 0:57 Thomas Deutschmann
2016-08-10 20:44 Thomas Deutschmann
2016-08-10 20:44 Thomas Deutschmann
2016-08-04 8:45 Jeroen Roovers
2016-06-21 21:01 Michał Górny
2016-06-21 19:55 Michał Górny
2016-06-21 18:25 Markus Meier
2016-03-16 6:46 Ian Delaney
2016-03-16 6:46 Ian Delaney
2016-02-05 15:24 Lars Wendler
2015-12-25 15:13 Agostino Sarubbo
2015-12-21 6:42 Jeroen Roovers
2015-10-09 14:12 Lars Wendler
2015-08-21 11:56 Lars Wendler
2015-08-18 15:19 Lars Wendler
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=1518345246.49ea852de7cbd4be09009da4b5110603a4d6729c.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