From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [POLICY] Keywording/Stabilizing Bug Assignment Policy
Date: Tue, 17 Apr 2007 20:17:48 +0100 [thread overview]
Message-ID: <20070417201748.0cdbe732@snowflake> (raw)
In-Reply-To: <4625187A.4060403@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
On Tue, 17 Apr 2007 14:56:58 -0400
Doug Goldstein <cardoe@gentoo.org> wrote:
> Once all but the last arch has keyworded said package, it is
> acceptable and proper for a bug wrangler and/or maintainer/herd to
> re-assign the bug to the last remaining arch and they remove that
> arch from CC. They should add their herd/maintainer to the CC of the
> bug.
Since when? The only recent instances of people doing that that I've
seen are when people are deliberately trying to create bugspam...
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-17 19:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 18:56 [gentoo-dev] [POLICY] Keywording/Stabilizing Bug Assignment Policy Doug Goldstein
2007-04-17 19:17 ` Ciaran McCreesh [this message]
2007-04-17 19:19 ` Ned Ludd
2007-04-17 19:36 ` Doug Goldstein
2007-04-17 19:57 ` Sune Kloppenborg Jeppesen
2007-04-17 19:50 ` [gentoo-dev] Re: [gentoo-core] " Stefan Schweizer
2007-04-17 20:06 ` Bryan Østergaard
2007-04-17 20:06 ` [gentoo-dev] " Alin Năstac
2007-04-17 20:25 ` [gentoo-dev] Re: [gentoo-core] " Chris Gianelloni
2007-04-17 22:36 ` Vlastimil Babka
2007-04-18 13:39 ` Jim Ramsay
2007-04-18 13:57 ` Chris Gianelloni
2007-04-18 15:14 ` Jim Ramsay
2007-05-27 10:23 ` [gentoo-dev] STABLEREQ/KEYWORDREQ Keywords in bugzilla Vlastimil Babka
2007-05-27 10:39 ` Robin H. Johnson
2007-05-27 11:06 ` Vlastimil Babka
2007-04-17 20:07 ` [gentoo-dev] [POLICY] Keywording/Stabilizing Bug Assignment Policy Samuli Suominen
2007-04-18 13:59 ` Mart Raudsepp
2007-04-20 23:33 ` [gentoo-dev] " Ryan Hill
2007-04-21 2:55 ` Chris Gianelloni
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=20070417201748.0cdbe732@snowflake \
--to=ciaranm@ciaranm.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