From: Alex Legler <a3li@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC Bugzilla interaction guide for devs & editbugs users
Date: Mon, 6 Sep 2010 14:38:21 +0200 [thread overview]
Message-ID: <20100906143821.31f243df@mail.a3li.li> (raw)
In-Reply-To: <AANLkTikrYb9pkndtuWAag89XqjrQDM6rbsQFoe5gsiyU@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
On Mon, 6 Sep 2010 10:39:59 +0200, Dirkjan Ochtman <djc@gentoo.org>
wrote:
> [...]
> >
> > 2.2. Security bugs
> > The developer should comment, but ONLY members of the security team
> > should:
> > - change whiteboard
> > - add/remove arches
> > - change bug status/reso
>
> The arches can still remove themselves when they've done whatever they
> needed to do, right?
>
Of course.
--
Alex Legler | Gentoo Security / Ruby
a3li@gentoo.org | a3li@jabber.ccc.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-09-06 12:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 8:32 [gentoo-dev] RFC Bugzilla interaction guide for devs & editbugs users Robin H. Johnson
2010-09-06 8:39 ` Dirkjan Ochtman
2010-09-06 12:38 ` Alex Legler [this message]
2010-09-06 15:31 ` Michael Weber
2010-09-06 16:07 ` [gentoo-dev] " Christian Faulhammer
2010-09-06 21:24 ` Ryan Hill
2010-09-06 12:10 ` Christian Faulhammer
2010-09-06 12:36 ` Alex Legler
2010-09-07 20:47 ` [gentoo-dev] " Róbert Čerňanský
2010-09-07 21:30 ` Robin H. Johnson
2010-09-07 21:43 ` Andreas K. Huettel
2010-09-07 21:44 ` dev-random
2010-09-07 22:05 ` Pacho Ramos
2010-09-07 22:53 ` [gentoo-dev] " Duncan
2010-09-08 4:44 ` Ryan Hill
2010-09-10 16:32 ` [gentoo-dev] " Jeroen Roovers
2010-09-11 7:17 ` [gentoo-dev] " Duncan
2010-09-11 13:43 ` Jeroen Roovers
2010-09-11 21:58 ` [gentoo-dev] " Róbert Čerňanský
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=20100906143821.31f243df@mail.a3li.li \
--to=a3li@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