public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Bainbridge <chrb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bugzilla triage
Date: Wed, 28 Jul 2004 11:23:57 +0100	[thread overview]
Message-ID: <200407281123.57341.chrb@gentoo.org> (raw)
In-Reply-To: <1090998546.11795.29.camel@tom.tomaw.org>

On Wednesday 28 July 2004 08:09, Tom Wesley wrote:
> Hi,
>
> After following the calm, collected discussion of the Bug voting thread
> I have a simple question.
>
> Is it useful to anyone for a user (ie, me) regularly query recently
> added bugs and add comments like "This should not be blocker", "This is
> not and enhancement" were they see fit?
> I can't see that this would actually achieve a huge amount, as it would
> simply generate mass emails without actually doing a lot of tidying of
> bugzilla.

Not that useful. If you're interested in categorising bugs apply for dev 
status and get the power to manipulate those fields yourself.

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-07-28 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28  7:09 [gentoo-dev] Bugzilla triage Tom Wesley
2004-07-28 10:23 ` Chris Bainbridge [this message]
2004-07-28 14:11   ` Malte S. Stretz

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=200407281123.57341.chrb@gentoo.org \
    --to=chrb@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