public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bugzilla package list editing
Date: Tue, 02 May 2017 18:27:58 +0200	[thread overview]
Message-ID: <22653284.3FEFaAhpj6@pinacolada> (raw)
In-Reply-To: <84f7fb6d-7a42-00e7-6043-f05f895ee9e8@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

Am Dienstag, 2. Mai 2017, 13:05:38 CEST schrieb Chí-Thanh Christopher Nguyễn:
>
> Also very common is that he changes fully qualified package names (which
> is the correct syntax per [1]) into fully qualified package atoms (which
> is the legacy syntax). Bug 616260 is one such example.

That's one thing. And it's super annoying since the bugzilla e-mails try to 
provide a diff, but the result is for longer package lists unreadable and not 
helpful. 

Also, in some cases, additionally keywords were added and removed from the 
list without any further comment. Taking this possibility into account, one 
would have to check any BZ mail with a lot of attention. 

The much better alternative would be 
* Don't do any cosmetic changes. They are pointless for a bot-evaluated field.
* If you need additional keywords or want to drop something, leave one 
sentence on the bug with request and reason, and let maintainers sort out the 
package list field...



-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  parent reply	other threads:[~2017-05-02 16:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 10:29 [gentoo-dev] Bugzilla package list editing Mart Raudsepp
2017-05-02  0:31 ` Andreas K. Huettel
2017-05-02 10:20   ` Paweł Hajdan, Jr.
2017-05-02 11:05     ` Chí-Thanh Christopher Nguyễn
2017-05-02 12:32       ` Ulrich Mueller
2017-05-02 16:19         ` Andreas K. Huettel
2017-05-04 15:42         ` Jeroen Roovers
2017-05-04 16:07           ` Mike Gilbert
2017-05-05  6:02           ` Ulrich Mueller
2017-05-02 12:36       ` Lars Wendler
2017-05-02 16:27       ` Andreas K. Huettel [this message]
2017-05-02 16:30         ` Andreas K. Huettel
2017-05-04 15:26       ` Jeroen Roovers
2017-05-10 15:22   ` Mart Raudsepp
2017-05-10 15:33     ` David Seifert
2017-05-10 15:45       ` Kristian Fiskerstrand
2017-05-10 18:17         ` Michael Jones
2017-05-10 19:08           ` Rich Freeman
2017-05-10 19:24             ` William L. Thomson Jr.
2017-05-10 20:10               ` Rich Freeman
2017-05-10 19:20           ` Mart Raudsepp

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=22653284.3FEFaAhpj6@pinacolada \
    --to=dilfridge@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