> On Oct. 30, 2012, 8:01 p.m., Vishesh Handa wrote: > > Please commit as two patches. One for the read write lock, and the other > > for the syslinking. (Plus, you'll need to fix the issue David raised)
Sure - I'm away from home right now, but I'll commit it next week (or whenever the power comes back). - Simeon ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/107082/#review21165 ----------------------------------------------------------- On Oct. 27, 2012, 6:29 p.m., Simeon Bird wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://git.reviewboard.kde.org/r/107082/ > ----------------------------------------------------------- > > (Updated Oct. 27, 2012, 6:29 p.m.) > > > Review request for Nepomuk, Vishesh Handa and Sebastian Trueg. > > > Description > ------- > > Some fairly trivial misc improvements to the filewatch service. Probably > don't make a big difference, but probably a good idea. > > - Use QReadWriteLock instead of QMutex in FileIndexerConfig, thus allowing > multiple threads to call shouldFolderBeIndexed at once (not that we really do > that right now). > > - Add the IN_EXCL_UNLINK inotify flag. On recent (2.6.36) kernels, this means > we don't generate events for files once > they have been unlinked from the directory we are watching. Prevents waking > up for some already-deleted temporary files. > > > Diffs > ----- > > services/fileindexer/fileindexerconfig.h 7debaf3 > services/fileindexer/fileindexerconfig.cpp 5226a79 > services/filewatch/kinotify.h 6e3f1c0 > services/filewatch/kinotify.cpp 9868b90 > > Diff: http://git.reviewboard.kde.org/r/107082/diff/ > > > Testing > ------- > > Compiled, ran for a bit, didn't seem to break anything. > > > Thanks, > > Simeon Bird > >
_______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
