From: "Ville Syrjälä" <syrjala@sci.fi>
To: public-mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@hugh.gmane.org
Cc: Evgeniy Polyakov
<public-zbr-i6C2adt8DTjR7s880joybQ@hugh.gmane.org>,
Christoph Hellwig <public-hch-jcswGhMUV9g@hugh.gmane.org>,
Robert Love <public-rlove-L7G0xEPcOZbYtjvyW6yDsg@hugh.gmane.org>,
public-linux-api-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org,
public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org,
Andrew Morton
<public-akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@hugh.gmane.org>,
public-john-jueV0HHMeujJJrXXpGQQMAC/G2K4zDHf@hugh.gmane.org
Subject: Re: [take 3] Use pid in inotify events.
Date: Thu, 20 Nov 2008 21:17:59 +0200 [thread overview]
Message-ID: <20081120191759.GH31176@sci.fi> (raw)
In-Reply-To: <cfd18e0f0811190643j7769f768q53889bbc950ef251@mail.gmail.com>
On Wed, Nov 19, 2008 at 09:43:41AM -0500, Michael Kerrisk wrote:
> I think what is really needed at this point is some consideration of
> what other extensions (if any) might be desired for inotify, and how
> we might be best create a design that suits those and future needs.
In case people are taking notes for "inotify ng" I have one improvement
request. Add some way to know when a move event is complete. Currently if
you're just wathing the source or target directory of a move you only get
one of the MOVED_FROM/MOVED_TO events. Not knowing whether you'll
eventually receive the other half of the event is problematic when you
want to treat such unpaired events the same as DELETE/CREATE events.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
next prev parent reply other threads:[~2008-11-20 20:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <acdcfe7e0811081035l56eedf05x8b3b7ee2fc01eee6@mail.gmail.com>
2008-11-08 18:40 ` [1/1] Use pid in inotify events Evgeniy Polyakov
2008-11-08 22:03 ` Evgeniy Polyakov
2008-11-10 15:13 ` [take 2] " Evgeniy Polyakov
2008-11-16 23:24 ` [take 3] " Evgeniy Polyakov
2008-11-17 16:59 ` Michael Kerrisk
2008-11-17 17:15 ` Evgeniy Polyakov
2008-11-17 17:23 ` Michael Kerrisk
2008-11-17 17:52 ` Evgeniy Polyakov
2008-11-20 13:09 ` Pavel Machek
2008-11-21 14:03 ` Evgeniy Polyakov
2008-11-21 14:20 ` Michael Kerrisk
2008-11-21 14:37 ` Evgeniy Polyakov
2008-11-21 14:30 ` Robert Love
2008-11-21 14:53 ` Evgeniy Polyakov
2008-11-21 14:57 ` Pavel Machek
2008-11-21 15:08 ` Evgeniy Polyakov
2008-11-18 13:19 ` Christoph Hellwig
2008-11-19 14:05 ` Evgeniy Polyakov
[not found] ` <cfd18e0f0811190634g276b4a2dm5b3d5de25a5c9222@mail.gmail.com>
2008-11-19 14:43 ` Michael Kerrisk
2008-11-20 19:17 ` Ville Syrjälä [this message]
2008-11-19 14:53 ` Evgeniy Polyakov
2008-11-20 22:34 ` John McCutchan
2008-11-20 23:06 ` Evgeniy Polyakov
2008-11-21 18:39 ` Arnd Bergmann
2008-11-22 7:12 ` David Newall
2008-11-22 9:41 ` Evgeniy Polyakov
2008-11-22 11:41 ` David Newall
2008-11-22 9:37 ` Evgeniy Polyakov
2008-11-24 5:08 ` John McCutchan
2008-11-24 7:30 ` Evgeniy Polyakov
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=20081120191759.GH31176@sci.fi \
--to=syrjala@sci.fi \
--cc=public-akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@hugh.gmane.org \
--cc=public-hch-jcswGhMUV9g@hugh.gmane.org \
--cc=public-john-jueV0HHMeujJJrXXpGQQMAC/G2K4zDHf@hugh.gmane.org \
--cc=public-linux-api-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org \
--cc=public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org \
--cc=public-mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@hugh.gmane.org \
--cc=public-rlove-L7G0xEPcOZbYtjvyW6yDsg@hugh.gmane.org \
--cc=public-zbr-i6C2adt8DTjR7s880joybQ@hugh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox