public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, Jan Kara <jack@suse.cz>,
	Matthew Bobrowski <repnop@google.com>,
	linux-man@vger.kernel.org
Subject: Re: [PATCH 0/2] fanotify man page updates for v5.17
Date: Fri, 17 Jun 2022 15:48:58 +0200	[thread overview]
Message-ID: <fd783262-e40c-d23d-cb99-8d6be1f479d1@gmail.com> (raw)
In-Reply-To: <20220617131158.1661235-1-amir73il@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1116 bytes --]

Hi Amir,

On 6/17/22 15:11, Amir Goldstein wrote:
[...]
> 
> I did not mention this course of events in the man page, because it
> seemed too much irrelevant information for end user, but am mentioning
> it here for full disclosure in case somebody thinks this information is
> relevant.

Hmm, maybe we should include it in the commit message?

I'll comment also on the patches, but mostly good stuff.

Cheers,

Alex

> 
> These patches apply on top of fan-fs-error branch in my tree [1]
> which you have already reviewed, but have not yet applied.
> 
> [1] https://github.com/amir73il/man-pages/commits/fan-fs-error
> 
> Amir Goldstein (2):
>    fanotify.7, fanotify_init.2: Document FAN_REPORT_TARGET_FID
>    fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_RENAME
> 
>   man2/fanotify_init.2 | 53 +++++++++++++++++++++++++++++++++++++++++---
>   man2/fanotify_mark.2 | 23 +++++++++++++++++++
>   man7/fanotify.7      | 31 ++++++++++++++------------
>   3 files changed, 90 insertions(+), 17 deletions(-)
> 

-- 
Alejandro Colomar
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-06-17 13:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 13:11 [PATCH 0/2] fanotify man page updates for v5.17 Amir Goldstein
2022-06-17 13:11 ` [PATCH 1/2] fanotify.7, fanotify_init.2: Document FAN_REPORT_TARGET_FID Amir Goldstein
2022-06-17 13:50   ` Alejandro Colomar
2022-06-17 13:11 ` [PATCH 2/2] fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_RENAME Amir Goldstein
2022-06-17 13:53   ` Alejandro Colomar
2022-06-17 14:00     ` Amir Goldstein
2022-06-17 13:48 ` Alejandro Colomar [this message]
2022-06-17 14:02   ` [PATCH 0/2] fanotify man page updates for v5.17 Amir Goldstein

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=fd783262-e40c-d23d-cb99-8d6be1f479d1@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=repnop@google.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