From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: games-puzzle/sgt-puzzles/
Date: Sun, 11 Feb 2018 10:53:25 +0000 (UTC) [thread overview]
Message-ID: <1518346345.a54aa1c54b1db645fd3fd301e7a740b23e394969.mgorny@gentoo> (raw)
commit: a54aa1c54b1db645fd3fd301e7a740b23e394969
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 10:47:14 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:52:25 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a54aa1c5
games-puzzle/sgt-puzzles: 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.
games-puzzle/sgt-puzzles/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/games-puzzle/sgt-puzzles/metadata.xml b/games-puzzle/sgt-puzzles/metadata.xml
index a434a63e3f4..744f27f1fda 100644
--- a/games-puzzle/sgt-puzzles/metadata.xml
+++ b/games-puzzle/sgt-puzzles/metadata.xml
@@ -8,7 +8,6 @@
<maintainer type="person">
<email>NP-Hardass@gentoo.org</email>
<name>NP-Hardass</name>
- <description>Co-maintainer; CC on all bugs</description>
</maintainer>
<use>
<flag name="gtk3">Use x11-libs/gtk+:3 instead of x11-libs/gtk+:2</flag>
next reply other threads:[~2018-02-11 10:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 10:53 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-30 21:11 [gentoo-commits] repo/gentoo:master commit in: games-puzzle/sgt-puzzles/ Andreas Sturmlechner
2021-05-30 21:11 Andreas Sturmlechner
2019-05-06 19:24 Göktürk Yüksek
2019-05-06 19:24 Göktürk Yüksek
2018-04-28 10:54 Jeroen Roovers
2018-04-28 10:30 Jeroen Roovers
2017-11-12 16:19 NP Hardass
2017-05-27 10:50 NP Hardass
2017-05-27 10:50 NP Hardass
2017-05-07 6:36 NP Hardass
2017-05-07 6:36 NP Hardass
2017-04-10 17:22 NP Hardass
2017-04-10 17:22 NP Hardass
2017-04-10 17:22 NP Hardass
2017-03-12 21:26 NP Hardass
2016-03-31 20:02 NP Hardass
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=1518346345.a54aa1c54b1db645fd3fd301e7a740b23e394969.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