linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
	Matthew Bobrowski <mbobrowski@mbobrowski.org>,
	linux-man@vger.kernel.org
Subject: [PATCH 0/3] fanotify man page updates for final v5.7
Date: Fri, 29 May 2020 12:25:27 +0300	[thread overview]
Message-ID: <20200529092530.25207-1-amir73il@gmail.com> (raw)

Hi Michael,

We made a last minute call to disable the FAN_DIR_MODIFY for v5.7.
Here is a man page update with some promissed cleanups.

Thanks,
Amir.

Amir Goldstein (3):
  Revert "fanotify.7, fanotify_mark.2: Document FAN_DIR_MODIFY"
  fanotify_init.2: move out of place entry FAN_REPORT_FID
  fanotify.7, fanotify_mark.2: Clarify FAN_ONDIR in output mask

 man2/fanotify_init.2 | 60 ++++++++++++++---------------
 man2/fanotify_mark.2 | 50 ++----------------------
 man7/fanotify.7      | 91 ++++++++++++++------------------------------
 3 files changed, 61 insertions(+), 140 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-05-29  9:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29  9:25 Amir Goldstein [this message]
2020-05-29  9:25 ` [PATCH 1/3] Revert "fanotify.7, fanotify_mark.2: Document FAN_DIR_MODIFY" Amir Goldstein
2020-06-07 12:15   ` Matthew Bobrowski
2020-06-08 20:13   ` Michael Kerrisk (man-pages)
2020-05-29  9:25 ` [PATCH 2/3] fanotify_init.2: move out of place entry FAN_REPORT_FID Amir Goldstein
2020-06-07 12:24   ` Matthew Bobrowski
2020-06-08 20:15   ` Michael Kerrisk (man-pages)
2020-05-29  9:25 ` [PATCH 3/3] fanotify.7, fanotify_mark.2: Clarify FAN_ONDIR in output mask Amir Goldstein
2020-06-07 12:40   ` Matthew Bobrowski
2020-06-08 20:18   ` Michael Kerrisk (man-pages)
2020-06-03 10:26 ` [PATCH 0/3] fanotify man page updates for final v5.7 Michael Kerrisk (man-pages)
2020-06-03 23:57   ` Matthew Bobrowski

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=20200529092530.25207-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).