public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC]: Proxy-maintainer project
Date: Thu, 18 Mar 2010 18:50:31 +0100	[thread overview]
Message-ID: <4BA267E7.8000805@gentoo.org> (raw)
In-Reply-To: <20100318102422.76188fc8@gentoo.org>

On 03/18/10 18:24, Sébastien Fabbro wrote:
> On Thursday 18 March, Markos Chandras wrote:
> 
>> 1) Should we use a new overlay? A new branch on sunrise? or work
>> ebuilds in Gentoo bugzilla?I think the latter is the best
>> 2) I think an email alias is not needed We can "monitor"
>> maintainer-wanted/- needed alias if needed. What do you think?
>> 3) Maybe a new KEYWORD needs to be added on bugzilla so ppl get
>> informed that the specific bug is already taking by another developer
>> and that somebody is working on it. So marking a bug with a keyword
>> e.g. "PROXY" might be useful.
> 
> 0) Switch portage cvs tree to
Sigh ... well, if "everyone" demands that ...

>multiple
... no, that's just silly. One tree to rule them all - we're even
folding the changes from the prefix project back in. Please don't
complexify things so they have enough Design ...

> git ones.
or something equivalent



  reply	other threads:[~2010-03-18 17:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 16:29 [gentoo-dev] [RFC]: Proxy-maintainer project Markos Chandras
2010-03-18 17:13 ` Alexis Ballier
2010-03-18 17:24 ` Sébastien Fabbro
2010-03-18 17:50   ` Patrick Lauer [this message]
2010-03-18 18:32   ` justin
2010-03-18 21:03   ` Angelo Arrifano
2010-03-18 21:22     ` Markos Chandras
2010-03-18 19:09 ` Thomas Sachau
2010-03-18 20:29   ` Markos Chandras
2010-03-18 20:34   ` Ben de Groot
2010-03-19 14:00     ` Richard Freeman
2010-03-19  8:05 ` Alex Alexander

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=4BA267E7.8000805@gentoo.org \
    --to=patrick@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