From: Joe Perches <joe@perches.com>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel@vger.kernel.org, rdunlap@infradead.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: rfc: fs directories without MAINTAINER section entries
Date: Wed, 05 Feb 2014 10:40:00 -0800 [thread overview]
Message-ID: <1391625600.30094.24.camel@joe-AO722> (raw)
In-Reply-To: <20140205175222.28d6788471b6551831440ed0@skynet.be>
On Wed, 2014-02-05 at 17:52 +0800, Fabian Frederick wrote:
> Adding generic fsdevel section for ADFS.
> I guess status can be considered 'orphan' like affs and befs.
and cramfs and efs and hfs and hfsplus too.
Other fs/ directories without MAINTAINERS sections:
fs/devpts
fs/exportfs
fs/isofs
fs/kernfs
fs/minix
fs/nls
fs/openpromfs
fs/proc
fs/qnx6
fs/ramfs
fs/romfs
Anyone have clues what to do with these?
Nothing?
Add new sections for each of them as Orphan?
Add new sections with Al as Maintained? </joke>
parent reply other threads:[~2014-02-05 18:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20140205175222.28d6788471b6551831440ed0@skynet.be>]
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=1391625600.30094.24.camel@joe-AO722 \
--to=joe@perches.com \
--cc=fabf@skynet.be \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).