From: Paul Varner <fuzzyray@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: ian@gentoo.org
Subject: Re: [gentoo-dev] Packages looking for proxy as ian no longer has commit access
Date: Mon, 28 Nov 2011 11:25:04 -0600 [thread overview]
Message-ID: <1322501104.7443.5.camel@beldin> (raw)
In-Reply-To: <20174.28666.291910.873897@a1i15.kph.uni-mainz.de>
On Thu, 2011-11-24 at 17:25 +0100, Ulrich Mueller wrote:
> >>>>> On Thu, 24 Nov 2011, Pacho Ramos wrote:
>
> > Due https://bugs.gentoo.org/show_bug.cgi?id=99016 ian doesn't
> > have commit access and, then, his packages need a proxy maintainer:
> > app-portage/autounmask
> > app-portage/demerge
>
> I would volunteer to proxy maintain these packages, if Christian still
> wants to be maintainer for them (his last commit was in 2009). If not,
> proxy maintainership doesn't make much sense.
>
Ulrich,
If we decide to proxy maintain these two packages, go ahead and add
tool-portage as the herd to back you up.
Regards,
Paul
prev parent reply other threads:[~2011-11-28 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 13:07 [gentoo-dev] Packages looking for proxy as ian no longer has commit access Pacho Ramos
2011-11-24 16:25 ` Ulrich Mueller
2011-11-28 17:25 ` Paul Varner [this message]
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=1322501104.7443.5.camel@beldin \
--to=fuzzyray@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ian@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