From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/centerim/
Date: Sun, 11 Feb 2018 11:02:45 +0000 (UTC) [thread overview]
Message-ID: <1518346909.e34aa0e4f5c8e05d2007405fea907ab3c8917fc4.mgorny@gentoo> (raw)
commit: e34aa0e4f5c8e05d2007405fea907ab3c8917fc4
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:01:49 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:01:49 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e34aa0e4
net-im/centerim: 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-im/centerim/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/net-im/centerim/metadata.xml b/net-im/centerim/metadata.xml
index 92fe867e708..a5a5d9728be 100644
--- a/net-im/centerim/metadata.xml
+++ b/net-im/centerim/metadata.xml
@@ -3,6 +3,5 @@
<pkgmetadata>
<maintainer type="person">
<email>swegener@gentoo.org</email>
- <description>Primary Maintainer</description>
</maintainer>
</pkgmetadata>
next reply other threads:[~2018-02-11 11:02 UTC|newest]
Thread overview: 9+ 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 --
2023-05-12 20:37 [gentoo-commits] repo/gentoo:master commit in: net-im/centerim/ Sven Wegener
2023-01-23 18:04 Arthur Zamarin
2023-01-23 18:04 Arthur Zamarin
2022-12-03 6:06 Sam James
2021-02-16 2:12 Matt Turner
2017-12-16 17:24 Tobias Klausmann
2017-10-30 9:02 Sven Wegener
2015-10-17 22:30 Manuel Rüger
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=1518346909.e34aa0e4f5c8e05d2007405fea907ab3c8917fc4.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