From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Stéphane Aulery" <saulery-GANU6spQydw@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: man5/filesystems.5: updated list and descriptions of supported filesystems
Date: Tue, 10 Mar 2015 06:57:49 +0100 [thread overview]
Message-ID: <54FE87DD.8090003@gmail.com> (raw)
In-Reply-To: <20150309182939.GA13767-GANU6spQydw@public.gmane.org>
On 03/09/2015 07:29 PM, Stéphane Aulery wrote:
> Hello Michael,
>
> Le mardi 03 mars 2015 à 01:14:25, Michael Kerrisk (man-pages) a écrit :
>>
>> On 03/03/2015 09:58 AM, saulery-GANU6spQydw@public.gmane.org wrote:
>>> From: Stéphane Aulery <saulery-GANU6spQydw@public.gmane.org>
>>
>> I appreciate the work your doing on man pages, but it would
>> be helpful if you could do the following:
>>
>> b) Send me a *list* of the filesystems you propose to add,
>> possibly with suggestions on how those FSes could be added
>> in patches that add multiple related FSes.
>
> Here is a list:
>
> adfs, afs, affs (five variants: DOS/0, DOS/1, DOS/2, DOS/3, DOS/4, DOS/5),
> befs, bfs, btrfs, ceph, cifs, coda, coherent, configfs, cramfs, debugfs,
> devpts, dlmfs, ecryptfs, efivarfs, exofs, f2fs, fat, gfs2, hfs, hfsplus,
> logfs, nilfs2, ocfs2, omfs, pohmelfs, qnx6, ramfs, reiserfs, romfs, spufs,
> spufs, squashfs, sysfs, tmpfs, ubifs, udf, ufs, v9fs, usbfs, xenix
Any ideas about ways of grouping these? I'd rather not receive one
patch with them all...
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-10 5:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 8:58 [patch] man5/filesystems.5: updated list and descriptions of supported saulery-GANU6spQydw
[not found] ` <1425373111-3584-1-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-03 8:58 ` man5/filesystems.5: updated list and descriptions of supported filesystems saulery-GANU6spQydw
[not found] ` <1425373111-3584-2-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-03 12:14 ` Michael Kerrisk (man-pages)
[not found] ` <54F5A5A1.7060401-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-03 13:17 ` Stéphane Aulery
[not found] ` <20150303131749.GA5522-GANU6spQydw@public.gmane.org>
2015-03-04 7:51 ` Michael Kerrisk (man-pages)
2015-03-09 18:29 ` Stéphane Aulery
[not found] ` <20150309182939.GA13767-GANU6spQydw@public.gmane.org>
2015-03-10 5:57 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <54FE87DD.8090003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-10 23:46 ` Stéphane Aulery
[not found] ` <20150310234652.GA2988-GANU6spQydw@public.gmane.org>
2015-03-11 5:49 ` Michael Kerrisk (man-pages)
2016-02-16 21:35 ` Bug#171681: " Stéphane Aulery
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=54FE87DD.8090003@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=saulery-GANU6spQydw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).