public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: bug wrangler queue is large...
Date: Wed, 26 May 2010 17:38:26 +0000	[thread overview]
Message-ID: <AANLkTimixP_wJwqSgjmlAdoOy9R5IDH77XfYLG_NnEmF@mail.gmail.com> (raw)
In-Reply-To: <pan.2010.05.26.09.27.07@cox.net>

On Wed, May 26, 2010 at 9:27 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> Jeroen Roovers posted on Wed, 26 May 2010 05:08:44 +0200 as excerpted:
>
>> On Tue, 25 May 2010 23:40:44 +0200
>> Harald van Dijk <truedfx@gentoo.org> wrote:
>>
>>> Yes, people like myself who don't normally wrangle bugs but try to help
>>> out occasionally. I'm not really interested in receiving all bug
>>> wrangler e-mails.
>>
>> Nobody should be required to read all that crap. :)
>
> I've often wished there was a way to flag a bug as "I'm not thru messing
> with it yet, don't mail anyone yet."  That's especially true when I know
> I'm going to be attaching 2-3 addition files, emerge --info, build log,
> maybe sth else like a config file or even a patch, where I know the
> wranglers are going to get all those extra mails.

Interesting, on most newer ticketing systems I've seen if you are
about to make a change there is typically some kind of UI element
(checkbox) that says something like 'suppress notifications.'  An
oft-used feature by me anyway when making cosmetic changes or making a
number of changes at once.  This assumes of course that anyone
interested in the bug will actually visit it to see the full set of
updates; not always the care for me and I imagine other users as well.

-A

>
> Or, if there was a way to attach files as part of the initial filing, but
> if there is, I've not found it.
>
> Alternatively, for normal bugs at least, maybe attaching emerge --info can
> be made a part of the process, with the post-submit note saying the bug
> won't be reported until that second step.  (Then for bugs that clearly
> don't need it, where the bug's clearly in an initscript or something, have
> a checkbox on that second step saying "emerge --info shouldn't be needed
> for this.")  That would both encourage emerge --info submission AND
> prevent one layer of bug spam at the same time! =:^)
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
>
>



  reply	other threads:[~2010-05-26 17:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  6:02 [gentoo-dev] bug wrangler queue is large Andreas K. Huettel
2010-05-25 18:24 ` Mike Frysinger
2010-05-25 18:46   ` Matti Bickel
2010-05-25 19:33     ` Mike Frysinger
2010-05-25 20:08       ` Harald van Dijk
2010-05-25 20:21         ` Matti Bickel
2010-05-25 20:25         ` Mike Frysinger
2010-05-25 21:40           ` Harald van Dijk
2010-05-26  3:08             ` Jeroen Roovers
2010-05-26  9:27               ` [gentoo-dev] " Duncan
2010-05-26 17:38                 ` Alec Warner [this message]
2010-05-26 20:42                 ` Jeroen Roovers
2010-07-15 22:50                 ` Markos Chandras
2010-07-15 23:38                   ` "Paweł Hajdan, Jr."
2010-07-19 18:01                   ` Jeroen Roovers
2010-07-19 18:05                     ` Alex Alexander
2010-07-19 18:08                       ` Pacho Ramos
2010-05-25 21:06         ` [gentoo-dev] " Matti Bickel
2010-05-25 22:03           ` Mike Frysinger
2010-05-26  5:36             ` Graham Murray
2010-05-26  9:01               ` [gentoo-dev] " Duncan
2010-05-26  9:08                 ` Matti Bickel
2010-05-26  3:05         ` [gentoo-dev] " Jeroen Roovers
2010-05-25 20:09       ` Matti Bickel
2010-05-26  3:02     ` Jeroen Roovers
2010-05-26  3:30       ` Jeroen Roovers
2010-05-26  7:42         ` Panagiotis Christopoulos
2010-05-25 19:33   ` Richard Freeman
2010-05-26  2:58   ` Jeroen Roovers
2010-05-26  4:25     ` Mike Frysinger

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=AANLkTimixP_wJwqSgjmlAdoOy9R5IDH77XfYLG_NnEmF@mail.gmail.com \
    --to=antarus@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