From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] proxy-maintainers herd as a backup herd for all the user-maintained packages
Date: Sun, 17 Mar 2013 16:46:33 +0000 [thread overview]
Message-ID: <CAG2jQ8hFdH-YdmSVxGPE=tUtJarFZGsaAS_02npFCxxncGFXfA@mail.gmail.com> (raw)
In-Reply-To: <CAG2jQ8hubwHqDcrspgeg19WqdtUL-zM-6M4ZHcBHZQjJZdping@mail.gmail.com>
On 17 March 2013 13:47, Markos Chandras <hwoarang@gentoo.org> wrote:
> On 5 March 2013 15:07, Jeroen Roovers <jer@gentoo.org> wrote:
>> 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.
>>
>> Sounds fine. I for one am converted (and the packages I maintain in
>> that fashion).
>>
>>
>> jer
>>
>
> This is happening today. There are about 390 packages that need fixing
> so I will take care all of them (and CC proxy-maint on open bugs as
> well)
>
> --
> Regards,
> Markos Chandras - Gentoo Linux Developer
> http://dev.gentoo.org/~hwoarang
Everything should now be in place. If you notice a problem please
either let me know or fix it yourself. Apologies for the bug-spam.
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
next prev parent reply other threads:[~2013-03-17 16:47 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 [this message]
2013-04-22 9:21 ` Alexis Ballier
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='CAG2jQ8hFdH-YdmSVxGPE=tUtJarFZGsaAS_02npFCxxncGFXfA@mail.gmail.com' \
--to=hwoarang@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