From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-video/ffdiaporama/
Date: Sun, 11 Feb 2018 11:02:44 +0000 (UTC) [thread overview]
Message-ID: <1518346870.88579414b7e9a011aa7dc5cd9694dbf37af5b20b.mgorny@gentoo> (raw)
commit: 88579414b7e9a011aa7dc5cd9694dbf37af5b20b
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 11:01:10 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 11:01:10 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=88579414
media-video/ffdiaporama: 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.
media-video/ffdiaporama/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/media-video/ffdiaporama/metadata.xml b/media-video/ffdiaporama/metadata.xml
index 60cbff526e1..84064cda742 100644
--- a/media-video/ffdiaporama/metadata.xml
+++ b/media-video/ffdiaporama/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>olivier.laurantin@laposte.net</email>
<name>Olivier Laurantin</name>
- <description>Proxy maintainer. CC him on bugs</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2018-02-11 11:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 11:02 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-11 9:04 [gentoo-commits] repo/gentoo:master commit in: media-video/ffdiaporama/ Ionen Wolkens
2025-02-02 15:03 Andreas Sturmlechner
2025-01-31 7:56 Joonas Niilola
2025-01-30 18:47 Jakov Smolić
2024-02-29 13:48 Joonas Niilola
2024-02-29 13:48 Joonas Niilola
2023-08-20 19:35 Arthur Zamarin
2023-08-20 19:34 Arthur Zamarin
2023-05-28 7:28 Joonas Niilola
2023-05-16 8:55 Andreas Sturmlechner
2023-05-16 8:36 Andreas Sturmlechner
2023-05-16 3:43 Sam James
2023-05-16 3:39 Sam James
2023-05-16 3:39 Sam James
2022-10-27 12:55 Joonas Niilola
2022-05-19 2:20 Sam James
2022-05-13 20:04 Sam James
2021-04-28 6:42 Joonas Niilola
2020-07-28 14:29 Andreas Sturmlechner
2020-04-26 10:16 Mikle Kolyada
2019-06-04 22:00 Andreas Sturmlechner
2019-06-04 20:58 Thomas Deutschmann
2019-05-29 1:15 Aaron Bauman
2018-12-22 11:43 Andreas Sturmlechner
2018-12-22 11:43 Andreas Sturmlechner
2018-01-15 19:03 Tobias Klausmann
2018-01-13 23:28 Andreas Sturmlechner
2017-12-21 20:29 Patrice Clement
2017-12-10 14:20 Jonas Stein
2017-11-26 23:11 David Seifert
2017-03-19 17:59 Amy Liffey
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=1518346870.88579414b7e9a011aa7dc5cd9694dbf37af5b20b.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