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: app-editors/qhexedit2/
Date: Sun, 11 Feb 2018 10:01:25 +0000 (UTC)	[thread overview]
Message-ID: <1518343278.218474ef0a34cb48350a7b586e6a3badba584802.mgorny@gentoo> (raw)

commit:     218474ef0a34cb48350a7b586e6a3badba584802
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 11 09:55:41 2018 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 11 10:01:18 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=218474ef

app-editors/qhexedit2: 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-editors/qhexedit2/metadata.xml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/app-editors/qhexedit2/metadata.xml b/app-editors/qhexedit2/metadata.xml
index 3f610e098d9..67f1531f77a 100644
--- a/app-editors/qhexedit2/metadata.xml
+++ b/app-editors/qhexedit2/metadata.xml
@@ -4,7 +4,6 @@
     <maintainer type="person">
         <email>coyote@bks.tv</email>
         <name>Victor Kustov</name>
-        <description>Proxied-maintainer. Assign bugs to him</description>
     </maintainer>
     <maintainer type="person">
         <email>zlogene@gentoo.org</email>


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

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11 10:01 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-21 16:21 [gentoo-commits] repo/gentoo:master commit in: app-editors/qhexedit2/ Rick Farina
2024-05-21 16:21 Rick Farina
2024-05-21 16:21 Rick Farina
2023-03-09  8:38 Joonas Niilola
2022-06-09  9:42 David Seifert
2022-06-01  1:56 Sam James
2022-06-01  1:55 Sam James
2022-05-31  2:55 Sam James
2022-04-21  6:51 Joonas Niilola
2022-04-21  6:51 Joonas Niilola
2022-04-10 21:11 Jonas Stein
2021-10-29 13:31 Yixun Lan
2021-10-27 12:54 Sam James
2021-10-27  6:50 Sam James
2021-06-01 18:28 Andrew Ammerlaan
2021-03-08 10:26 Sam James
2021-03-08 10:25 Sam James
2020-12-04  3:28 Rick Farina
2020-03-17  1:52 Rick Farina
2020-02-11 11:38 Michał Górny
2018-11-25 16:04 Mikle Kolyada
2018-04-16 21:12 David Seifert
2018-01-11 16:15 Mikle Kolyada

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=1518343278.218474ef0a34cb48350a7b586e6a3badba584802.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