From: Markos Chandras <hwoarang@gentoo.org>
To: Alexis Ballier <aballier@gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] proxy-maintainers herd as a backup herd for all the user-maintained packages
Date: Mon, 22 Apr 2013 10:25:48 +0100 [thread overview]
Message-ID: <CAG2jQ8g0Y20XOELHTWo8ody8NOwGESjC=ubPnFbnN76NFi640w@mail.gmail.com> (raw)
In-Reply-To: <20130422112129.1bd9fde6@portable>
On 22 April 2013 10:21, Alexis Ballier <aballier@gentoo.org> wrote:
> 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 ?
Up to you but it will help us track packages maintained by users so we
can find another maintainer if they ever go MIA.
>
> 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.
I made it clear on my previous emails that we do not intend to touch
packages maintained by other @gentoo people or herds unless
proxy-maint is the only herd in metadata. If someone violated that,
then it's best to inform him about this, in case he forgot.
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
next prev parent reply other threads:[~2013-04-22 9:26 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
2013-04-22 9:25 ` Markos Chandras [this message]
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='CAG2jQ8g0Y20XOELHTWo8ody8NOwGESjC=ubPnFbnN76NFi640w@mail.gmail.com' \
--to=hwoarang@gentoo.org \
--cc=aballier@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