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: sys-apps/bleachbit/
Date: Sun, 11 Feb 2018 11:12:23 +0000 (UTC)	[thread overview]
Message-ID: <1518347306.628d6d93dd18c96b57c6c4a7efe6f9bbda1c8e32.mgorny@gentoo> (raw)

commit:     628d6d93dd18c96b57c6c4a7efe6f9bbda1c8e32
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:08:26 2018 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:08:26 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=628d6d93

sys-apps/bleachbit: 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.

 sys-apps/bleachbit/metadata.xml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/sys-apps/bleachbit/metadata.xml b/sys-apps/bleachbit/metadata.xml
index 5c059a4ab56..1ba6f1e4b71 100644
--- a/sys-apps/bleachbit/metadata.xml
+++ b/sys-apps/bleachbit/metadata.xml
@@ -4,7 +4,6 @@
 	<maintainer type="person">
 		<email>christian.tietz@mailbox.org</email>
 		<name>Christian Tietz</name>
-		<description>Proxy Maintainer</description>
 	</maintainer>
 	<maintainer type="project">
 		<email>proxy-maint@gentoo.org</email>


             reply	other threads:[~2018-02-11 11:12 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11 11:12 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-21 21:25 [gentoo-commits] repo/gentoo:master commit in: sys-apps/bleachbit/ Sam James
2025-04-02 16:58 Sam James
2025-04-02 16:58 Sam James
2024-11-05 15:13 Joonas Niilola
2024-04-24 12:51 Conrad Kostecki
2024-03-21  2:50 Sam James
2024-01-08  7:57 Joonas Niilola
2024-01-08  7:39 Joonas Niilola
2023-11-22 17:44 Sam James
2023-04-29 22:19 Conrad Kostecki
2023-04-28 17:29 Sam James
2023-04-28 17:29 Sam James
2023-02-27 12:33 Michał Górny
2022-05-23 19:34 Conrad Kostecki
2022-05-23 12:04 Jakov Smolić
2022-05-23 12:04 Jakov Smolić
2021-11-24  8:07 Joonas Niilola
2021-11-24  8:07 Joonas Niilola
2021-11-24  8:07 Joonas Niilola
2021-07-08 17:21 Ionen Wolkens
2021-06-15  7:27 Joonas Niilola
2021-02-24 16:27 Sam James
2021-02-21  8:10 Sam James
2021-02-19 12:07 Sam James
2021-02-19  2:41 Sam James
2021-01-12 15:53 Sam James
2020-06-02  4:33 Aaron Bauman
2020-05-28 15:45 Agostino Sarubbo
2020-05-28 15:37 Agostino Sarubbo
2020-04-21 12:45 Joonas Niilola
2020-04-21 12:45 Joonas Niilola
2020-04-01 14:38 Joonas Niilola
2020-04-01 14:38 Joonas Niilola
2019-12-04  0:41 Aaron Bauman
2019-12-03 10:06 Agostino Sarubbo
2019-12-03 10:03 Agostino Sarubbo
2019-10-29  6:22 Joonas Niilola
2019-10-29  6:22 Joonas Niilola
2019-10-10  5:22 Joonas Niilola
2019-06-08  7:48 Michał Górny
2019-06-04 20:58 Thomas Deutschmann
2019-04-19 21:44 Michał Górny
2019-04-19 21:44 Michał Górny
2019-04-19 21:44 Michał Górny
2019-03-02  0:04 Andreas Sturmlechner
2018-04-06  2:38 Aaron Bauman
2018-04-06  2:38 Aaron Bauman
2018-04-05 13:17 Aaron Bauman
2018-03-05 16:15 Michał Górny
2018-03-05 16:15 Michał Górny
2018-01-03 11:06 Patrice Clement
2017-12-29 19:54 Craig Andrews
2017-12-29 19:54 Craig Andrews
2017-03-12 19:31 Patrice Clement
2017-03-12 19:31 Patrice Clement
2017-01-03 23:07 Patrice Clement
2016-08-06  8:12 Pacho Ramos
2016-07-08 18:20 Patrice Clement
2016-06-16  6:58 Patrice Clement
2016-06-11 20:20 Patrice Clement
2016-06-11 20:20 Patrice Clement
2016-05-22 15:07 Patrice Clement

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=1518347306.628d6d93dd18c96b57c6c4a7efe6f9bbda1c8e32.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