From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Felix_Schulte-dDVk9ABzqyjQT0dZR+AlfA@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Bug in documentation
Date: Sun, 21 Jul 2013 00:28:13 +0200 [thread overview]
Message-ID: <51EB0EFD.40706@gmail.com> (raw)
In-Reply-To: <94A07449C751564EBBCDD7481A3E829E104E60-vsg8/t6Ur8szk0z/ZuOLCTkPmBWM+Ckf2LY78lusg7I@public.gmane.org>
On 07/19/13 13:37, Felix_Schulte-dDVk9ABzqyjQT0dZR+AlfA@public.gmane.org wrote:
> Hi!
>
> The documentation for inotify is a bit misleading
> (http://man7.org/linux/man-pages/man7/inotify.7.html)
>
> It says when describing the "mask" field:
> IN_MOVED_FROM File moved out of watched directory (*).
>
> The description is not correct, since this event is also fired (on
> read()) when a file is moved *within* the same directory (to a new name)
> and is explicitly *not* *moved out* of the directory.
>
> It's not a big deal, of course, I just was confused about it recently.
Hello Felix,
I agree, it could be clearer. I revised the text to read:
IN_MOVED_FROM Generated for the directory containing the
old filename when a file is renamed (*).
IN_MOVED_TO Generated for the directory containing the
new filename when a file is renamed (*).
Okay?
Cheers,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-07-20 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 11:37 Bug in documentation Felix_Schulte-dDVk9ABzqyjQT0dZR+AlfA
[not found] ` <94A07449C751564EBBCDD7481A3E829E104E60-vsg8/t6Ur8szk0z/ZuOLCTkPmBWM+Ckf2LY78lusg7I@public.gmane.org>
2013-07-20 22:28 ` Michael Kerrisk [this message]
[not found] ` <51EB0EFD.40706-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-07-23 9:30 ` Felix_Schulte-dDVk9ABzqyjQT0dZR+AlfA
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=51EB0EFD.40706@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Felix_Schulte-dDVk9ABzqyjQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.