From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Keno Fischer <keno@juliacomputing.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, Nikolaus Rath <nikolaus@rath.org>
Subject: Re: [PATCH] fuse.4: Add new file describing /dev/fuse
Date: Sun, 11 Dec 2016 10:27:02 +0100 [thread overview]
Message-ID: <4e6f4ec4-a8e6-67c8-bf21-29cf16652880@gmail.com> (raw)
In-Reply-To: <CABV8kRxw+Dps3iMi8GJOUiegUdxFBuaMF-icy=z0=faKUNi4SA@mail.gmail.com>
Hi Keno,
On 12/10/2016 10:03 PM, Keno Fischer wrote:
> Hi Michael, your edits look good to me.
Thanks for checking.
> Here's some suggested wording
> to address the FIXMEs. Hope that's clearer (I also hope this goes
> through ok, gmail sometimes mangles patches, so I usually send them
> from the command line).
Thanks. Applied.
I screwed my branch up, so had to create a new one, which
has the current version.
http://git.kernel.org/cgit/docs/man-pages/man-pages.git/log/?h=draft_2_fuse
I wonder if we might get some input from Miklos on this page?
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2016-12-11 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 7:20 [PATCH] fuse.4: Add new file describing /dev/fuse Keno Fischer
2016-12-10 14:17 ` Michael Kerrisk (man-pages)
2016-12-10 21:03 ` Keno Fischer
2016-12-11 9:27 ` Michael Kerrisk (man-pages) [this message]
2016-12-10 21:13 ` Nikolaus Rath
2016-12-10 21:19 ` Keno Fischer
2016-12-11 9:28 ` Michael Kerrisk (man-pages)
2016-12-11 15:31 ` Nikolaus Rath
2016-12-11 18:16 ` Michael Kerrisk (man-pages)
2016-12-11 19:55 ` Nikolaus Rath
2016-12-12 6:21 ` Michael Kerrisk (man-pages)
2016-12-13 17:49 ` Nikolaus Rath
2016-12-14 7:25 ` Michael Kerrisk (man-pages)
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=4e6f4ec4-a8e6-67c8-bf21-29cf16652880@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=keno@juliacomputing.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=nikolaus@rath.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).