From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: hwoarang@gentoo.org
Subject: Re: [gentoo-dev] proxy-maintainers herd as a backup herd for all the user-maintained packages
Date: Mon, 22 Apr 2013 11:21:29 +0200 [thread overview]
Message-ID: <20130422112129.1bd9fde6@portable> (raw)
In-Reply-To: <CAG2jQ8g8z+bNQzu_3xqeB-HKUsPE1RVNkmH31jXakdQxxZV4rg@mail.gmail.com>
Sorry for bringing back this thread from the dead, but...
On Tue, 5 Mar 2013 09:09:47 +0000
Markos Chandras <hwoarang@gentoo.org> wrote:
> If there is at least one Gentoo developer in metadata.xml we assume
> the package is properly maintained by him so
> we never touch it.
Does this include herd ?
For ml stuff, I usually put ml herd + non-gentoo proxy maint, meaning:
anyone with some knowledge of ml (ie in the herd) can commit, there is
no specific communication method with the non-gentoo maintainer, so
there is no need for me to be listed there.
Now, these packages have proxy-maint as co-herd, and I'd prefer people
that are not familiar with ml (ebuilds have their set of specificities)
not to blindly commit packages because it's proxy-maintained.
Alexis.
next prev parent reply other threads:[~2013-04-22 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 19:35 [gentoo-dev] proxy-maintainers herd as a backup herd for all the user-maintained packages Markos Chandras
2013-03-05 3:41 ` Jeroen Roovers
2013-03-05 9:09 ` Markos Chandras
2013-03-05 15:07 ` Jeroen Roovers
2013-03-17 13:47 ` Markos Chandras
2013-03-17 16:46 ` Markos Chandras
2013-04-22 9:21 ` Alexis Ballier [this message]
2013-04-22 9:25 ` Markos Chandras
2013-04-22 9:36 ` Alexis Ballier
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=20130422112129.1bd9fde6@portable \
--to=aballier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=hwoarang@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