From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Matthew Bobrowski <mbobrowski@mbobrowski.org>,
Michael Kerrisk <mtk.manpages@gmail.com>, Jan Kara <jack@suse.cz>,
linux-man <linux-man@vger.kernel.org>,
Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: Re: [PATCH v2 0/4] fanotify man page updates for v5.13
Date: Fri, 10 Dec 2021 14:56:37 +0100 [thread overview]
Message-ID: <e1b659e8-7efe-a6e2-6fdb-0ed4f4b29b7c@gmail.com> (raw)
In-Reply-To: <CAOQ4uxhuBm6oMGNVmtsrgErbbrTcd72Xuib5Fv=yfySbpqFoKg@mail.gmail.com>
Hi, Amir!
On 12/10/21 10:37, Amir Goldstein wrote:
> On Mon, Nov 22, 2021 at 6:57 PM Alejandro Colomar (man-pages)
> <alx.manpages@gmail.com> wrote:
>> Patch set applied.
>> See some tweaks below.
>>
>
> I understand that the patches were applied to your github tree main branch [1]
Yes.
>
> Should we regard that branch as the "next" branch and base our next
> fanotify man page updates (i.e. FAN_REPORT_PIDFD) on top of it?
And yes.
Thanks,
Alex
--
Alejandro Colomar
Linux man-pages maintainer; https://www.kernel.org/doc/man-pages/
prev parent reply other threads:[~2021-12-10 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 17:12 [PATCH v2 0/4] fanotify man page updates for v5.13 Amir Goldstein
2021-11-20 17:12 ` [PATCH v2 1/4] fanotify_init.2, fanotify_mark.2: Document unprivileged listener Amir Goldstein
2021-11-20 17:19 ` Amir Goldstein
2021-11-20 17:12 ` [PATCH v2 2/4] fanotify_init.2, fanotify_mark.2, fanotify.7: Configurable limits Amir Goldstein
2021-11-20 17:19 ` Amir Goldstein
2021-11-20 17:12 ` [PATCH v2 3/4] fanotify_mark.2: Update w.r.t tmpfs support Amir Goldstein
2021-11-20 17:12 ` [PATCH v2 4/4] fanotify_init.2: Document kernel commits Amir Goldstein
2021-11-22 16:56 ` [PATCH v2 0/4] fanotify man page updates for v5.13 Alejandro Colomar (man-pages)
2021-12-10 9:37 ` Amir Goldstein
2021-12-10 13:56 ` Alejandro Colomar (man-pages) [this message]
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=e1b659e8-7efe-a6e2-6fdb-0ed4f4b29b7c@gmail.com \
--to=alx.manpages@gmail.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=krisman@collabora.com \
--cc=linux-man@vger.kernel.org \
--cc=mbobrowski@mbobrowski.org \
--cc=mtk.manpages@gmail.com \
/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