From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apps/otrs/
Date: Sun, 11 Feb 2018 11:36:43 +0000 (UTC) [thread overview]
Message-ID: <1518348992.b1f85d02736d794f3c4068e3e631637603a3139a.mgorny@gentoo> (raw)
commit: b1f85d02736d794f3c4068e3e631637603a3139a
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:21:10 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:36:32 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b1f85d02
www-apps/otrs: 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.
www-apps/otrs/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/www-apps/otrs/metadata.xml b/www-apps/otrs/metadata.xml
index 8bdf83b248a..9c04a8ca23c 100644
--- a/www-apps/otrs/metadata.xml
+++ b/www-apps/otrs/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>lists@xunil.at</email>
<name>Stefan Weichinger</name>
- <description>Proxy maintainer</description>
</maintainer>
<maintainer type="project">
<email>web-apps@gentoo.org</email>
next reply other threads:[~2018-02-11 11:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 11:36 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-08 16:53 [gentoo-commits] repo/gentoo:master commit in: www-apps/otrs/ David Seifert
2018-10-29 14:22 Miroslav Šulc
2018-10-29 14:22 Miroslav Šulc
2018-05-16 15:52 Andreas Sturmlechner
2018-05-08 20:13 Mikle Kolyada
2018-05-08 20:00 Mikle Kolyada
2018-02-15 14:27 Patrice Clement
2018-01-02 19:12 Thomas Deutschmann
2017-12-06 12:54 Michael Palimaka
2017-11-26 23:26 David Seifert
2017-10-07 19:49 Patrice Clement
2017-10-02 22:32 Patrice Clement
2017-08-02 9:07 Patrice Clement
2017-06-06 11:53 Thomas Deutschmann
2017-06-06 11:53 Thomas Deutschmann
2017-05-31 16:46 Patrice Clement
2017-04-09 23:10 Göktürk Yüksek
2017-03-12 9:15 Michał Górny
2017-03-12 9:15 Michał Górny
2017-03-12 9:05 Michał Górny
2017-01-25 23:29 Patrice Clement
2017-01-25 23:29 Patrice Clement
2015-10-05 8:13 Ian Delaney
2015-10-05 8:06 Ian Delaney
2015-10-01 4:58 Ian Delaney
2015-08-14 1:11 Chris Reffett
2015-08-14 1:07 Chris Reffett
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=1518348992.b1f85d02736d794f3c4068e3e631637603a3139a.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