public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apps/tt-rss/
Date: Sun, 11 Feb 2018 11:36:43 +0000 (UTC)	[thread overview]
Message-ID: <1518348993.d8c6e1d3ec95cc1c4e58f19d2aba0f3381b59396.mgorny@gentoo> (raw)

commit:     d8c6e1d3ec95cc1c4e58f19d2aba0f3381b59396
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:21:14 2018 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:36:33 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d8c6e1d3

www-apps/tt-rss: 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/tt-rss/metadata.xml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/www-apps/tt-rss/metadata.xml b/www-apps/tt-rss/metadata.xml
index 388039cd655..6605b067508 100644
--- a/www-apps/tt-rss/metadata.xml
+++ b/www-apps/tt-rss/metadata.xml
@@ -4,7 +4,6 @@
 	<maintainer type="person">
 		<email>chewi@gentoo.org</email>
 		<name>James Le Cuirot</name>
-		<description>Maintainer</description>
 	</maintainer>
 	<use>
 		<flag name="daemon">Install additional init scripts for automated RSS updates</flag>


             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 --
2024-10-12 15:01 [gentoo-commits] repo/gentoo:master commit in: www-apps/tt-rss/ James Le Cuirot
2024-02-11 22:37 James Le Cuirot
2023-09-19  7:59 James Le Cuirot
2022-12-09 23:36 James Le Cuirot
2022-10-08  9:51 James Le Cuirot
2022-08-04 16:53 James Le Cuirot
2022-01-02 14:09 Florian Schmaus
2022-01-02 14:09 Florian Schmaus
2021-02-13 13:02 James Le Cuirot
2021-01-10 22:27 Sam James
2020-09-23 21:42 James Le Cuirot
2020-09-23 21:42 James Le Cuirot
2019-05-27 21:18 James Le Cuirot
2019-05-26 21:01 James Le Cuirot
2018-01-18 13:44 James Le Cuirot
2017-11-26 23:26 David Seifert
2017-01-07 15:56 James Le Cuirot
2016-10-12 21:26 Thomas Kahle
2016-10-12  7:38 Thomas Kahle
2016-09-30 11:46 Thomas Kahle
2016-09-30 11:46 Thomas Kahle
2016-05-27 11:46 Thomas Kahle
2016-05-27 11:46 Thomas Kahle
2016-01-24 15:21 Thomas Kahle
2016-01-24 15:21 Thomas Kahle
2015-09-24 12:24 Thomas Kahle
2015-09-24 12:24 Thomas Kahle

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=1518348993.d8c6e1d3ec95cc1c4e58f19d2aba0f3381b59396.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