From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/mcabber/
Date: Sun, 11 Feb 2018 11:02:45 +0000 (UTC) [thread overview]
Message-ID: <1518346913.88e1c170820eab4b9980453169a0e349f9b598ef.mgorny@gentoo> (raw)
commit: 88e1c170820eab4b9980453169a0e349f9b598ef
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:01:53 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:01:53 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=88e1c170
net-im/mcabber: 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/mcabber/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/net-im/mcabber/metadata.xml b/net-im/mcabber/metadata.xml
index 5a98c0903af..bef971e1d17 100644
--- a/net-im/mcabber/metadata.xml
+++ b/net-im/mcabber/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>wschlich@gentoo.org</email>
<name>Wolfram Schlich</name>
- <description>Secondary maintainer</description>
</maintainer>
<longdescription lang="en">
MCabber is a small Jabber console client that features
next reply other threads:[~2018-02-11 11:02 UTC|newest]
Thread overview: 45+ 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-04-15 3:10 [gentoo-commits] repo/gentoo:master commit in: net-im/mcabber/ Sam James
2022-04-13 14:46 Sam James
2022-02-16 21:53 David Seifert
2021-01-05 18:59 Andreas K. Hüttel
2020-11-20 1:34 Thomas Deutschmann
2020-11-19 22:58 Sam James
2020-10-19 6:57 Andrey Utkin
2020-10-19 6:57 Andrey Utkin
2020-02-24 13:11 Agostino Sarubbo
2020-02-18 16:24 Agostino Sarubbo
2020-02-02 19:35 Mart Raudsepp
2019-12-31 0:48 Andrey Utkin
2019-12-31 0:48 Andrey Utkin
2019-02-25 20:13 Andrey Utkin
2019-02-18 19:29 Andrey Utkin
2018-11-03 17:18 Mikle Kolyada
2018-10-28 21:29 Thomas Deutschmann
2018-09-23 1:10 Andrey Utkin
2018-09-23 1:10 Andrey Utkin
2018-09-23 1:10 Andrey Utkin
2018-09-23 1:10 Andrey Utkin
2018-09-23 1:10 Andrey Utkin
2018-07-10 20:04 Andrey Utkin
2018-04-30 20:37 Andreas Hüttel
2018-03-15 21:35 Andrey Utkin
2018-01-07 14:58 Ulrich Müller
2017-07-11 0:30 Aaron Bauman
2017-07-11 0:30 Aaron Bauman
2017-06-21 8:04 Wolfram Schlich
2017-02-17 10:42 Agostino Sarubbo
2017-02-17 10:15 Agostino Sarubbo
2017-02-16 16:19 Wolfram Schlich
2016-12-27 16:49 Wolfram Schlich
2016-12-21 15:51 Wolfram Schlich
2016-12-13 16:29 Wolfram Schlich
2016-12-13 11:30 Agostino Sarubbo
2016-12-13 11:05 Agostino Sarubbo
2016-11-22 11:32 Wolfram Schlich
2016-09-19 16:09 Wolfram Schlich
2016-09-19 16:05 Wolfram Schlich
2016-03-29 7:13 Wolfram Schlich
2016-02-06 18:02 Wolfram Schlich
2016-02-06 17:28 Wolfram Schlich
2016-01-27 11:05 Wolfram Schlich
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=1518346913.88e1c170820eab4b9980453169a0e349f9b598ef.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