public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stefan Schweizer <genstef@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Fw: [gentoo-core] [POLICY] Keywording/Stabilizing Bug Assignment Policy
Date: Wed, 18 Apr 2007 01:55:07 +0200	[thread overview]
Message-ID: <f03mp6$1p9$1@sea.gmane.org> (raw)
In-Reply-To: 20070418003741.25ef86b2@epia.jer-c2.orkz.net

Jeroen Roovers wrote:
> On Tue, 17 Apr 2007 21:50:26 +0200
> "Stefan Schweizer" <genstef@gentoo.org> wrote:
>> As a maintainer I have to deal with many stable/keywording requests.
>> Those are bugs that generally hang around in my bugzilla queries and
>> fill my mailbox and I do not have any ability to help there or fix
>> them. Those bugmails constitute spam for my mailbox.
> 
> The bugs you open generate too much information? So basically you do
> too much work to still cope with the consequences of that very same
> work? Maybe you can get a dev to act as your secretary? (I am being
> serious.)

They generate irrelevant information for me because I cannot help with
stabling. So I would love to have the possibility to -CC me there after
siging the stabling off.

>> It would be cool to implement a keywording@gentoo.org alias just to
>> assign those bugs to so that we maintainers do not need to see them.
> 
> So this way you would avoid receiving important information?

The information is not important to me, the headlines are just filling my
mailbox

> Why don't 
> you set up bugsy not to inform you about these under [Email
> Preferences]?

This is possible? How can I separate keywording/stable and normal bugs in a
general way?

> [..] so IMHO only the package maintainer should ever (yet diligently)
> clean up so-called "old" ebuilds.

or the package maintainer can put a REMOVEOLD keyword on the bug or
something to make obvious that he wants it removed. I would love this
possibility :)

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-04-17 23:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 22:37 [gentoo-dev] Fw: [gentoo-core] [POLICY] Keywording/Stabilizing Bug Assignment Policy Jeroen Roovers
2007-04-17 23:55 ` Stefan Schweizer [this message]
2007-04-18  9:09   ` [gentoo-dev] " Matti Bickel

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='f03mp6$1p9$1@sea.gmane.org' \
    --to=genstef@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