From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Stephen Kitt <steve@sk2.org>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Giuseppe Scrivano <gscrivan@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] close_range.2: new page documenting close_range(2)
Date: Sun, 21 Mar 2021 16:38:59 +0100 [thread overview]
Message-ID: <4eb789d0-5914-23ae-3ab9-cbfa9b6b9622@gmail.com> (raw)
In-Reply-To: <20210309205309.7e2568c9@heffalump.sk2.org>
On 3/9/21 8:53 PM, Stephen Kitt wrote:
> Hi Michael,
>
> On Thu, 28 Jan 2021 21:50:23 +0100, "Michael Kerrisk (man-pages)"
> <mtk.manpages@gmail.com> wrote:
>> Thanks for your patch revision. I've merged it, and have
>> done some light editing, but I still have a question:
>
> Does this need anything more? I don’t see it in the man-pages repo.
Sorry, Stephen. It's just me being slow. I've made a few edits,
replaced the example program with another that more clearly allows
the user to see what's going on, and pushed to Git.
Thanks,
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:[~2021-03-21 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 16:11 [PATCH v6] close_range.2: new page documenting close_range(2) Stephen Kitt
2021-01-28 20:50 ` Michael Kerrisk (man-pages)
2021-01-28 22:10 ` Stephen Kitt
[not found] ` <20210129100024.m4bil5mz5prry4iq@wittgenstein>
2021-03-21 15:31 ` Michael Kerrisk (man-pages)
2021-01-29 10:01 ` Christian Brauner
2021-03-09 19:53 ` Stephen Kitt
2021-03-21 15:38 ` Michael Kerrisk (man-pages) [this message]
2021-03-22 21:31 ` Stephen Kitt
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=4eb789d0-5914-23ae-3ab9-cbfa9b6b9622@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=gscrivan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=steve@sk2.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).