From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/barnyard2/
Date: Sun, 11 Feb 2018 11:02:44 +0000 (UTC) [thread overview]
Message-ID: <1518346874.5618a0dcde8fb06a6b79d76ba5076d083dabd0df.mgorny@gentoo> (raw)
commit: 5618a0dcde8fb06a6b79d76ba5076d083dabd0df
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:01:14 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:01:14 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5618a0dc
net-analyzer/barnyard2: 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.
net-analyzer/barnyard2/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/net-analyzer/barnyard2/metadata.xml b/net-analyzer/barnyard2/metadata.xml
index be80ad6bbcb..c97636709d3 100644
--- a/net-analyzer/barnyard2/metadata.xml
+++ b/net-analyzer/barnyard2/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>patrick@gentoo.org</email>
<name>Patrick Lauer</name>
- <description>Maintainer</description>
</maintainer>
<maintainer type="project">
<email>netmon@gentoo.org</email>
next reply other threads:[~2018-02-11 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 11:02 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-12 15:28 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/barnyard2/ Sam James
2021-03-12 15:25 Sam James
2019-07-06 9:11 Jeroen Roovers
2019-02-08 14:27 Brian Evans
2018-11-08 22:52 Patrice Clement
2017-10-29 14:38 Jonas Stein
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=1518346874.5618a0dcde8fb06a6b79d76ba5076d083dabd0df.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