From: Matthew Thode <prometheanfire@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Herd likely up for grabs: net-fs
Date: Tue, 19 Jan 2016 14:46:28 -0600 [thread overview]
Message-ID: <569EA0A4.9000607@gentoo.org> (raw)
In-Reply-To: <569C8020.10402@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
On 01/18/2016 12:03 AM, Joshua Kinard wrote:
> On 01/17/2016 15:03, Michał Górny wrote:
>> Hello, everyone.
>>
>> The current maintainer of net-fs herd so far hasn't replied to our
>> queries. If we don't get any reply in a week, we will be disbanding it
>> and looking for new maintainers for its packages.
>>
>> Is anyone interested in keeping the herd as a whole and maintaining all
>> of its packages? If nobody replies till 2016-01-24, the herd will be
>> automatically disbanded and I will be sending a complete list of
>> packages needing maintainers.
>>
>> Packages currently in herd along with their other maintainers:
>>
>
> [snip]
>
>> net-fs/ncpfs :
>
> I'll claim this one. I actually have several old NetWare VMs (3.x, 4.2) that I
> can test this with from time-to-time, both TCP/IP and old IPX.
>
>
>> net-fs/nfs4-acl-tools :
>> net-fs/nfs-utils :
>> net-nds/rpcbind :
>> net-libs/libnfsidmap :
>
> base-system has portmap already, and given some run nfs as a root filesystem, I
> wonder if base-system shouldn't cover these as well?
>
> --J
>
>
I'd like to help out as I use nfs as well, but don't think I can do it
myself, just a user...
--
-- Matthew Thode (prometheanfire)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-01-19 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 20:03 [gentoo-dev] Herd likely up for grabs: net-fs Michał Górny
2016-01-18 6:03 ` Joshua Kinard
2016-01-19 20:46 ` Matthew Thode [this message]
2016-01-20 17:27 ` Mike Frysinger
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=569EA0A4.9000607@gentoo.org \
--to=prometheanfire@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