From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/dblatex/
Date: Sun, 11 Feb 2018 10:25:04 +0000 (UTC) [thread overview]
Message-ID: <1518344697.85f4fa43e9198790c1dbf3168b2dd96fa49027ca.mgorny@gentoo> (raw)
commit: 85f4fa43e9198790c1dbf3168b2dd96fa49027ca
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 10:21:33 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:24:57 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=85f4fa43
app-text/dblatex: 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.
app-text/dblatex/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/app-text/dblatex/metadata.xml b/app-text/dblatex/metadata.xml
index 33912835a88..609cf12fd1e 100644
--- a/app-text/dblatex/metadata.xml
+++ b/app-text/dblatex/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>zoltan@sinustrom.info</email>
<name>Zoltan Puskas</name>
- <description>Proxied maintainer. Assign bugs to him.</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2018-02-11 10:25 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 10:25 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-19 23:55 [gentoo-commits] repo/gentoo:master commit in: app-text/dblatex/ Sam James
2024-12-09 7:20 Arthur Zamarin
2024-10-17 5:49 Joonas Niilola
2024-10-14 7:16 Florian Schmaus
2024-10-13 11:43 Jakov Smolić
2024-06-13 10:37 Michał Górny
2024-06-13 10:37 Michał Górny
2023-12-23 18:24 Sam James
2023-12-23 18:24 Sam James
2023-12-23 18:24 Sam James
2023-12-17 17:40 Arthur Zamarin
2023-12-17 17:40 Arthur Zamarin
2023-12-16 9:28 Joonas Niilola
2023-12-16 8:06 Joonas Niilola
2023-11-13 7:34 Sam James
2023-05-20 5:09 Sam James
2023-05-01 9:53 Sam James
2023-05-01 7:55 Arthur Zamarin
2023-04-05 19:09 Sam James
2023-04-05 10:10 Arthur Zamarin
2023-04-05 9:30 Arthur Zamarin
2023-04-05 9:30 Arthur Zamarin
2023-04-05 8:40 Arthur Zamarin
2023-04-05 7:01 Matthew Smith
2023-04-05 6:56 Matthew Smith
2023-03-05 6:34 WANG Xuerui
2022-11-13 11:39 Sam James
2022-10-08 17:09 Sam James
2022-09-27 21:44 Sam James
2022-06-10 6:49 Sam James
2022-03-20 19:08 Arthur Zamarin
2021-08-22 10:26 Marek Szuba
2021-05-29 15:33 Sam James
2021-03-08 14:15 Sam James
2021-02-25 4:18 Sam James
2021-02-25 3:55 Sam James
2021-02-22 18:57 Sam James
2021-02-21 19:50 Sam James
2021-02-21 9:55 Sam James
2021-02-19 0:44 Sam James
2021-02-17 7:36 Sergei Trofimovich
2021-02-16 18:39 Sam James
2021-02-16 18:39 Sam James
2021-02-11 7:36 Sergei Trofimovich
2021-02-10 18:26 Sam James
2021-02-01 18:04 Sergei Trofimovich
2020-09-04 15:17 Sam James
2020-09-02 0:19 Sam James
2020-08-05 12:19 Joonas Niilola
2020-04-13 17:21 Agostino Sarubbo
2020-04-13 14:49 Agostino Sarubbo
2020-04-13 14:48 Agostino Sarubbo
2020-03-03 6:03 Joonas Niilola
2019-01-23 13:41 Mikle Kolyada
2018-04-09 19:30 Andreas Sturmlechner
2018-01-10 6:19 Markus Meier
2018-01-08 22:05 Mikle Kolyada
2015-11-15 10:57 Alexis Ballier
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=1518344697.85f4fa43e9198790c1dbf3168b2dd96fa49027ca.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