From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libtar/
Date: Sun, 11 Feb 2018 10:36:45 +0000 (UTC) [thread overview]
Message-ID: <1518345251.7fe3940344b96e06d8c74f62344afcb5c91dee49.mgorny@gentoo> (raw)
commit: 7fe3940344b96e06d8c74f62344afcb5c91dee49
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 10:31:13 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:34:11 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7fe39403
dev-libs/libtar: 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/libtar/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/dev-libs/libtar/metadata.xml b/dev-libs/libtar/metadata.xml
index 37ba3f50a32..f434dfea382 100644
--- a/dev-libs/libtar/metadata.xml
+++ b/dev-libs/libtar/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>sdnick484@gmail.com</email>
<name>Nick Andrade</name>
- <description>Active Maintainer, Assign bugs</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2018-02-11 10:36 UTC|newest]
Thread overview: 22+ 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 --
2023-05-28 20:03 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libtar/ Arthur Zamarin
2023-05-28 19:29 Arthur Zamarin
2023-05-28 18:59 Arthur Zamarin
2023-05-28 18:56 Arthur Zamarin
2023-05-28 18:56 Arthur Zamarin
2022-07-27 20:10 David Seifert
2021-08-20 23:23 Marek Szuba
2019-03-20 20:27 Aaron Bauman
2018-05-20 19:10 Andreas Sturmlechner
2018-05-19 10:41 Sergei Trofimovich
2018-04-07 21:30 Sergei Trofimovich
2018-03-06 8:17 Jonas Stein
2018-03-04 10:19 Jason Zaman
2018-03-04 6:51 Thomas Deutschmann
2018-02-28 7:15 Sergei Trofimovich
2018-02-17 13:37 Andreas Sturmlechner
2017-07-13 7:48 Alexis Ballier
2017-07-12 17:08 Alexis Ballier
2017-05-30 7:00 Alexis Ballier
2015-09-06 6:18 Jeroen Roovers
2015-08-26 7:28 Agostino Sarubbo
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=1518345251.7fe3940344b96e06d8c74f62344afcb5c91dee49.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