From: Matthew Bobrowski <repnop@google.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
Gabriel Krisman Bertazi <krisman@collabora.com>,
linux-man <linux-man@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH RESEND v5] fanotify.7, fanotify_mark.2: Document FAN_FS_ERROR
Date: Mon, 23 May 2022 21:50:42 +0000 [thread overview]
Message-ID: <YowBsihg5Zwo6CfS@google.com> (raw)
In-Reply-To: <e8daa69c-8f07-6fe7-8e63-96e23f8deec6@gmail.com>
On Sun, May 22, 2022 at 11:37:25PM +0200, Alejandro Colomar wrote:
> Hi Amir,
>
> On 5/22/22 18:12, Amir Goldstein wrote:
> > It is applied on top of:
> >
> > https://lore.kernel.org/linux-man/20220514131346.10171-1-alx.manpages@gmail.com/T/#u
>
> Okay, I see that other one is pending some rewording, so I'll hold this one.
>
> >
> > We have a rather long backlog of man page updates pending merge
> > from Matthew, Gabriel and myself.
> > We need to merge them by order.
> > The entire stack is available in [BRANCHES] on my github tree [1].
> >
> > Let me summarize it for you again:
>
> Thanks. I'll write here what I know about the, just to be sure I didn't
> miss anything. If you need anything from me, please tell me.
>
> >
> > FAN_REPORT_PIDFD v5.15 [fanotify_pidfd]
>
> Pending a rewording of a paragraph.
Right, I'll get around to this at some point today.
/M
next prev parent reply other threads:[~2022-05-23 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 18:09 [PATCH RESEND v5] fanotify.7, fanotify_mark.2: Document FAN_FS_ERROR Gabriel Krisman Bertazi
2022-05-21 6:40 ` Amir Goldstein
2022-05-22 15:44 ` Alejandro Colomar
2022-05-22 16:12 ` Amir Goldstein
2022-05-22 21:37 ` Alejandro Colomar
2022-05-23 21:50 ` Matthew Bobrowski [this message]
2022-05-24 6:07 ` Matthew Bobrowski
2022-06-17 12:37 ` Amir Goldstein
2022-06-17 12:49 ` Alejandro Colomar
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=YowBsihg5Zwo6CfS@google.com \
--to=repnop@google.com \
--cc=alx.manpages@gmail.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=krisman@collabora.com \
--cc=linux-man@vger.kernel.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