From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-fs/openafs-kernel/
Date: Sun, 11 Feb 2018 11:02:45 +0000 (UTC) [thread overview]
Message-ID: <1518346900.9e2555ab5fb77f9d47a4b8fdf628370269fb8ceb.mgorny@gentoo> (raw)
commit: 9e2555ab5fb77f9d47a4b8fdf628370269fb8ceb
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:01:40 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:01:40 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9e2555ab
net-fs/openafs-kernel: 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-fs/openafs-kernel/metadata.xml | 2 --
1 file changed, 2 deletions(-)
diff --git a/net-fs/openafs-kernel/metadata.xml b/net-fs/openafs-kernel/metadata.xml
index 20e8e259583..e76fe2c4c44 100644
--- a/net-fs/openafs-kernel/metadata.xml
+++ b/net-fs/openafs-kernel/metadata.xml
@@ -3,11 +3,9 @@
<pkgmetadata>
<maintainer type="person">
<email>NP-Hardass@gentoo.org</email>
- <description>please assign bugs to</description>
</maintainer>
<maintainer type="person">
<email>bircoph@gentoo.org</email>
<name>Andrew Savchenko</name>
- <description>please CC on bugs</description>
</maintainer>
</pkgmetadata>
next reply other threads:[~2018-02-11 11:02 UTC|newest]
Thread overview: 47+ 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 --
2020-11-29 19:14 [gentoo-commits] repo/gentoo:master commit in: net-fs/openafs-kernel/ Andrew Savchenko
2020-08-08 12:18 Mikle Kolyada
2018-03-02 4:41 NP Hardass
2018-03-02 4:41 NP Hardass
2018-03-02 4:41 NP Hardass
2017-12-27 22:01 NP Hardass
2017-12-11 19:16 NP Hardass
2017-12-11 19:06 NP Hardass
2017-12-11 19:06 NP Hardass
2017-09-23 1:23 NP Hardass
2017-09-22 15:45 NP Hardass
2017-09-22 15:45 NP Hardass
2017-09-13 19:48 NP Hardass
2017-06-01 10:33 NP Hardass
2017-05-13 9:55 Andrew Savchenko
2017-05-12 14:55 Agostino Sarubbo
2017-05-04 15:55 Agostino Sarubbo
2017-05-01 13:37 Agostino Sarubbo
2017-02-12 10:48 Andrew Savchenko
2017-02-08 17:38 NP Hardass
2016-12-25 22:45 Andrew Savchenko
2016-12-25 10:09 Agostino Sarubbo
2016-12-24 10:18 Agostino Sarubbo
2016-12-21 9:40 Tobias Klausmann
2016-08-11 4:29 NP Hardass
2016-08-11 4:29 NP Hardass
2016-08-01 12:17 Andrew Savchenko
2016-08-01 12:17 Andrew Savchenko
2016-07-23 22:01 Andrew Savchenko
2016-07-22 10:59 Andrew Savchenko
2016-07-20 16:40 NP Hardass
2016-04-30 14:05 Andrew Savchenko
2016-04-30 0:29 Andrew Savchenko
2016-03-26 19:15 Andrew Savchenko
2016-03-26 15:52 Agostino Sarubbo
2016-03-26 15:52 Agostino Sarubbo
2016-03-26 15:51 Agostino Sarubbo
2016-03-23 10:40 NP Hardass
2016-03-22 22:11 NP Hardass
2016-02-23 9:56 Andrew Savchenko
2015-11-03 19:07 Andrew Savchenko
2015-11-03 19:07 Andrew Savchenko
2015-10-16 8:09 Agostino Sarubbo
2015-09-24 2:07 NP Hardass
2015-09-06 8:32 Agostino Sarubbo
2015-08-16 14:21 Mikle Kolyada
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=1518346900.9e2555ab5fb77f9d47a4b8fdf628370269fb8ceb.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