From: Stefan Schweizer <genstef@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] maintainer-wanted buglist needs attention
Date: Thu, 3 Nov 2005 20:40:45 +0100 [thread overview]
Message-ID: <e79639220511031140g761bd16ah60b72931da1cba07@mail.gmail.com> (raw)
In-Reply-To: <20051103192413.449b67e5@snowdrop.home>
On 11/3/05, Ciaran McCreesh <ciaranm@gentoo.org> wrote:
> I can also give you a list of people who throw hissy fits if you dare
> suggest that their code may be anything less than perfect... It's a
> pretty useful starting point for filtering out the worst of the
> dross...
Do you have a list of people who contribute more than one ebuild and
might want to be a developer?
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-03 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 16:42 [gentoo-dev] maintainer-wanted buglist needs attention Tom Martin
2005-11-03 16:57 ` Carsten Lohrke
2005-11-03 17:06 ` Sebastian Bergmann
2005-11-03 17:17 ` Mike Frysinger
2005-11-03 17:30 ` Carsten Lohrke
2005-11-03 19:24 ` Ciaran McCreesh
2005-11-03 19:40 ` Stefan Schweizer [this message]
2005-11-03 19:49 ` Ciaran McCreesh
2005-11-04 7:19 ` Norguhtar
2005-11-04 20:21 ` Nattfodd
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=e79639220511031140g761bd16ah60b72931da1cba07@mail.gmail.com \
--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