Matthias Clasen ac78d14125 inotify: Fix handling of paired events for atomic replace ... After the big file monitoring rewrite, we only put the IN_MOVED_FROM event in the queue for such pairs. It matches INOTIFY_DIR_MASK and thus we call ip_dispatch_event on it, but that function was filtering it out because the filename in the 'from' event is the one of the temp file, not the one we are monitoring. That name is in the 'to' event, so compare it as well, and let the event passin that case. There is another instance of this check in glocalfilemonitor.c, which is corrected here as well. https://bugzilla.gnome.org/show_bug.cgi?id=751358		2015-08-19 14:57:53 -04:00
..
ginotifydirectorymonitor.c	substantially rework file monitors	2015-03-20 11:59:47 -04:00
ginotifydirectorymonitor.h	Updated FSF's address	2014-01-31 14:31:55 +01:00
ginotifyfilemonitor.c	substantially rework file monitors	2015-03-20 11:59:47 -04:00
ginotifyfilemonitor.h	substantially rework file monitors	2015-03-20 11:59:47 -04:00
inotify-helper.c	inotify: implement "boredom" algorithm	2015-03-20 12:01:35 -04:00
inotify-helper.h	Updated FSF's address	2014-01-31 14:31:55 +01:00
inotify-kernel.c	inotify: fix move event matching accounting	2015-03-26 14:56:25 -04:00
inotify-kernel.h	inotify: implement "boredom" algorithm	2015-03-20 12:01:35 -04:00
inotify-missing.c	Updated FSF's address	2014-01-31 14:31:55 +01:00
inotify-missing.h	Updated FSF's address	2014-01-31 14:31:55 +01:00
inotify-path.c	inotify: Fix handling of paired events for atomic replace	2015-08-19 14:57:53 -04:00
inotify-path.h	inotify: implement "boredom" algorithm	2015-03-20 12:01:35 -04:00
inotify-sub.c	substantially rework file monitors	2015-03-20 11:59:47 -04:00
inotify-sub.h	substantially rework file monitors	2015-03-20 11:59:47 -04:00
Makefile.am	substantially rework file monitors	2015-03-20 11:59:47 -04:00