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: dev-util/clion/
Date: Sun, 11 Feb 2018 10:53:24 +0000 (UTC)	[thread overview]
Message-ID: <1518346301.8da9bbd214a301f4f38d3cef3223002f84982bdf.mgorny@gentoo> (raw)

commit:     8da9bbd214a301f4f38d3cef3223002f84982bdf
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 10:46:45 2018 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:51:41 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8da9bbd2

dev-util/clion: 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.

 dev-util/clion/metadata.xml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/dev-util/clion/metadata.xml b/dev-util/clion/metadata.xml
index 781668ce179..4f7225e07bb 100644
--- a/dev-util/clion/metadata.xml
+++ b/dev-util/clion/metadata.xml
@@ -4,7 +4,6 @@
 	<maintainer type="person">
 		<email>c.a.strahl@gmail.com</email>
 		<name>Christian Strahl</name>
-		<description>Proxy maintainer. Assign bugs to him.</description>
 	</maintainer>
 	<maintainer type="project">
 		<email>proxy-maint@gentoo.org</email>


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

Thread overview: 127+ 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 --
2025-01-27  6:45 [gentoo-commits] repo/gentoo:master commit in: dev-util/clion/ Viorel Munteanu
2025-01-05 13:07 Florian Schmaus
2024-10-26 15:00 Viorel Munteanu
2024-06-11 17:04 Ulrich Müller
2024-05-25  5:05 Arthur Zamarin
2024-05-13 17:33 Ulrich Müller
2024-05-13 16:11 Ulrich Müller
2024-04-14  9:57 Viorel Munteanu
2024-04-14  9:57 Viorel Munteanu
2023-07-14  6:50 Joonas Niilola
2023-07-14  6:50 Joonas Niilola
2023-04-10 10:41 Joonas Niilola
2023-04-10 10:41 Joonas Niilola
2023-02-24 15:09 Joonas Niilola
2023-02-10  8:57 Joonas Niilola
2023-02-10  8:57 Joonas Niilola
2023-02-09 15:53 Joonas Niilola
2023-01-12 14:07 Joonas Niilola
2022-12-23 10:22 Viorel Munteanu
2022-11-22 13:55 Joonas Niilola
2022-09-14 17:17 Matthew Smith
2022-09-10  8:27 Matthew Smith
2022-07-05  9:06 Joonas Niilola
2022-07-05  9:06 Joonas Niilola
2022-06-14  7:13 Joonas Niilola
2022-06-14  7:13 Joonas Niilola
2022-06-03 13:15 Joonas Niilola
2022-06-03 13:15 Joonas Niilola
2022-06-03 13:15 Joonas Niilola
2022-01-28  8:36 Sam James
2022-01-28  8:36 Sam James
2021-12-24  4:47 Sam James
2021-12-24  4:47 Sam James
2021-08-14  5:59 Joonas Niilola
2021-08-14  5:59 Joonas Niilola
2021-08-14  5:59 Joonas Niilola
2021-07-02  7:38 Joonas Niilola
2021-07-02  7:38 Joonas Niilola
2021-04-13 10:38 Joonas Niilola
2021-04-13 10:38 Joonas Niilola
2021-04-13 10:38 Joonas Niilola
2021-03-23 12:32 Joonas Niilola
2021-03-23 12:32 Joonas Niilola
2021-02-15 13:15 Joonas Niilola
2021-02-15 13:15 Joonas Niilola
2021-02-15 13:15 Joonas Niilola
2021-01-05  8:40 Joonas Niilola
2021-01-05  8:40 Joonas Niilola
2021-01-04 12:34 Joonas Niilola
2020-10-17 13:19 Joonas Niilola
2020-10-17 13:19 Joonas Niilola
2020-10-08  6:57 Joonas Niilola
2020-10-08  6:57 Joonas Niilola
2020-08-21  7:15 Joonas Niilola
2020-08-21  7:15 Joonas Niilola
2020-08-21  7:15 Joonas Niilola
2020-07-07 13:30 Joonas Niilola
2020-07-07 13:30 Joonas Niilola
2020-05-13 13:17 Joonas Niilola
2020-05-13 13:17 Joonas Niilola
2020-04-16  8:11 Joonas Niilola
2020-04-16  8:11 Joonas Niilola
2020-03-26  7:22 Joonas Niilola
2020-03-26  7:22 Joonas Niilola
2020-02-06  6:20 Joonas Niilola
2020-02-06  6:20 Joonas Niilola
2020-02-06  6:20 Joonas Niilola
2020-01-20 13:03 Joonas Niilola
2020-01-20 13:03 Joonas Niilola
2019-11-30  7:50 Joonas Niilola
2019-11-30  7:50 Joonas Niilola
2019-10-18  5:25 Joonas Niilola
2019-10-18  5:25 Joonas Niilola
2019-10-13 12:36 Joonas Niilola
2019-10-13 12:36 Joonas Niilola
2019-09-26 16:41 Ulrich Müller
2019-09-26 16:41 Ulrich Müller
2019-09-15 16:49 Joonas Niilola
2019-09-15 16:49 Joonas Niilola
2019-07-30  3:33 Georgy Yakovlev
2019-07-30  3:33 Georgy Yakovlev
2019-05-10 18:25 Georgy Yakovlev
2019-05-10 18:25 Georgy Yakovlev
2019-04-16 18:27 Georgy Yakovlev
2019-04-16 18:27 Georgy Yakovlev
2019-02-15 23:12 Patrice Clement
2019-02-15 23:12 Patrice Clement
2019-01-31 18:52 Georgy Yakovlev
2019-01-31 18:52 Georgy Yakovlev
2019-01-31 18:52 Georgy Yakovlev
2018-11-27 22:41 Georgy Yakovlev
2018-11-27 22:41 Georgy Yakovlev
2018-09-23 17:45 Georgy Yakovlev
2018-09-23 17:45 Georgy Yakovlev
2018-08-06 15:47 Georgy Yakovlev
2018-08-06 15:47 Georgy Yakovlev
2018-08-06 15:47 Georgy Yakovlev
2018-08-06 15:47 Georgy Yakovlev
2018-03-30 21:27 Michał Górny
2018-03-30 21:27 Michał Górny
2018-03-24 15:34 Michał Górny
2018-03-24 15:34 Michał Górny
2018-02-17 15:26 Patrice Clement
2018-02-17 15:26 Patrice Clement
2018-01-05 23:57 Craig Andrews
2018-01-05 23:57 Craig Andrews
2017-12-02 22:53 Patrice Clement
2017-12-02 22:53 Patrice Clement
2017-10-15 21:11 Patrice Clement
2017-10-15 21:11 Patrice Clement
2017-09-02 17:30 Patrice Clement
2017-09-02 17:30 Patrice Clement
2017-08-05 11:08 Michał Górny
2017-08-05 11:08 Michał Górny
2017-07-20 20:30 Patrice Clement
2017-07-20 20:30 Patrice Clement
2017-06-12 21:46 Patrice Clement
2017-06-12 21:46 Patrice Clement
2017-05-21 18:53 Michał Górny
2017-05-21 18:53 Michał Górny
2017-04-26 14:04 Michał Górny
2017-04-26 14:04 Michał Górny
2017-04-13 13:12 Patrice Clement
2017-04-13 13:12 Patrice Clement
2016-08-11  8:35 Patrice Clement
2016-03-09  9:49 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=1518346301.8da9bbd214a301f4f38d3cef3223002f84982bdf.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