From: Ioannis Aslanidis <aslanidis@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Marking bugs for bugday?
Date: Tue, 2 Mar 2010 01:15:50 +0100 [thread overview]
Message-ID: <ea440b1d1003011615h54be8c26ie3ef58bf2b2f1db7@mail.gmail.com> (raw)
In-Reply-To: <20100302010205.18765d7s0e4x781s@webmail.df.eu>
That sounds great!
On Tue, Mar 2, 2010 at 1:02 AM, Sebastian Pipping <sping@gentoo.org> wrote:
>
> Quoting Ioannis Aslanidis <aslanidis@gmail.com>:
>>
>> I would prefer to keep the keyword for
>> Bugday Members to administer.
>
> I don't think that sending mails would work well.
> If you want extra control/QA for bugday team members
> I would propose two different keywords: one for bugday
> candidates and one for confirmed bugday bugs.
>
> Any dev could mark bugs as candidates easily and without
> delays while you could still reserve acknoledgement to you.
>
>
>
> Sebastian
>
>
>
>
>
--
Ioannis Aslanidis
http://www.deathwing00.org
<deathwing00[at]gentoo.org> 0x47F370A0
next prev parent reply other threads:[~2010-03-02 1:04 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 4:18 [gentoo-dev] Marking bugs for bugday? Sebastian Pipping
2010-02-27 15:39 ` Roy Bamford
2010-02-27 17:42 ` Sebastian Pipping
2010-02-27 16:22 ` Mark Loeser
2010-02-27 17:38 ` Sebastian Pipping
2010-02-27 18:14 ` Roy Bamford
2010-02-27 20:15 ` Sebastian Pipping
2010-02-27 20:46 ` Dale
2010-02-27 20:48 ` Mark Loeser
2010-02-27 21:45 ` Ben de Groot
2010-02-27 23:14 ` Mark Loeser
2010-02-28 9:36 ` Dawid Węgliński
2010-02-28 13:15 ` Alexander Færøy
2010-02-28 0:22 ` [gentoo-dev] " Ryan Hill
2010-02-28 19:54 ` [gentoo-dev] " Markos Chandras
2010-02-28 20:04 ` Sebastian Pipping
2010-03-01 1:35 ` Joshua Saddler
2010-03-01 21:17 ` Ioannis Aslanidis
2010-03-01 22:19 ` Ben de Groot
2010-03-01 22:26 ` Ioannis Aslanidis
2010-03-02 0:02 ` Sebastian Pipping
2010-03-02 0:15 ` Ioannis Aslanidis [this message]
2010-03-02 1:09 ` [gentoo-dev] " Duncan
2010-03-02 1:32 ` Alec Warner
2010-03-02 19:09 ` Sebastian Pipping
2010-03-02 19:08 ` Sebastian Pipping
2010-03-02 19:17 ` Ulrich Mueller
2010-03-02 19:28 ` Nathan Zachary
2010-03-02 19:39 ` Sebastian Pipping
2010-03-02 19:42 ` Nathan Zachary
2010-03-06 14:45 ` Robert Buchholz
2010-03-06 15:26 ` Ioannis Aslanidis
2010-03-06 19:09 ` David Leverton
2010-03-06 20:22 ` Ioannis Aslanidis
2010-03-07 4:30 ` Sebastian Pipping
2010-03-07 12:23 ` David Leverton
2010-03-08 3:19 ` Ryan Hill
2010-03-01 22:46 ` [gentoo-dev] " George Prowse
2010-03-01 22:48 ` Mark Loeser
2010-03-02 19:36 ` Sebastian Pipping
2010-03-02 20:47 ` Alec Warner
2010-03-02 21:05 ` Sebastian Pipping
2010-03-02 21:28 ` Alec Warner
2010-03-02 20:59 ` Ioannis Aslanidis
2010-03-04 19:13 ` Roy Bamford
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=ea440b1d1003011615h54be8c26ie3ef58bf2b2f1db7@mail.gmail.com \
--to=aslanidis@gmail.com \
--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