[Nepomuk] Review Request: FileWatcher: Check the mtime of the file for CloseOnWrite events
Sebastian Trueg
sebastian at trueg.de
Fri Aug 3 14:21:28 UTC 2012
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105839/#review16829
-----------------------------------------------------------
services/filewatch/nepomukfilewatch.cpp
<http://git.reviewboard.kde.org/r/105839/#comment13154>
Small optimization: move the shouldBeIndexed check above all else.
- Sebastian Trueg
On Aug. 3, 2012, 2:09 p.m., Vishesh Handa wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/105839/
> -----------------------------------------------------------
>
> (Updated Aug. 3, 2012, 2:09 p.m.)
>
>
> Review request for Nepomuk and Sebastian Trueg.
>
>
> Description
> -------
>
> Tons of applications open files in 'write' mode even though they have no
> intention of writing to them. When they close the file descriptor, it
> produces a CloseOnWrite event and the FileWatcher service would add it
> to the queue, and ask the fileindexer to index it.
>
>
> Diffs
> -----
>
> services/filewatch/nepomukfilewatch.cpp c998dc9
>
> Diff: http://git.reviewboard.kde.org/r/105839/diff/
>
>
> Testing
> -------
>
>
> Thanks,
>
> Vishesh Handa
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20120803/fc5abc1c/attachment.html>
More information about the Nepomuk
mailing list