From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] net-p2p/deluge needs a maintainer
Date: Sun, 31 Mar 2013 07:23:59 -0400 [thread overview]
Message-ID: <CAGfcS_k5BBmFCc-ocJdk12sf6Mr80ksK8z1Ue4FMGhX07srsKA@mail.gmail.com> (raw)
In-Reply-To: <CAG2jQ8horfj3x=VFJ3RDOq1ZhW_ePPg4dp7rUZxRTkQc-oi9Ow@mail.gmail.com>
On Sun, Mar 31, 2013 at 7:01 AM, Markos Chandras <hwoarang@gentoo.org> wrote:
> Hi,
>
> net-p2p/deluge has open bugs for years[1] and I don't see anybody from
> the net-p2p herd
> to actually maintain it. It would be nice to find a new dedicated
> maintainer for it. If a user is interested in helping us maintain it,
> please contact proxy-maint_at_gentoo_dot_org[2].
I'll potentially grab this one, though proxy maintainers are still
welcome (especially if you run it under openrc and would like to fix
some of the init.d bugs, as I do not due to its tendency to crash).
Thanks for calling for help prior to treecleaning...
Rich
next prev parent reply other threads:[~2013-03-31 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 11:01 [gentoo-dev] net-p2p/deluge needs a maintainer Markos Chandras
2013-03-31 11:23 ` Rich Freeman [this message]
2013-03-31 12:08 ` Markos Chandras
2013-03-31 12:11 ` Ian Whyman
2013-04-01 9:02 ` heroxbd
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=CAGfcS_k5BBmFCc-ocJdk12sf6Mr80ksK8z1Ue4FMGhX07srsKA@mail.gmail.com \
--to=rich0@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