Olivier Goffart 47710d167a SyncEngine: fix inode after move if the file has moved on the file system ... This is the fix for issue #4370 Step to reproduce the bug: 1) have lots of files in directory "dir1" 2) do mkdir dir2 && mv dir1/* dir2 3) DURING the sync (which takes time because of the many moves) do mkdir dir3 && mv dir2/* dir3/ 4) observe that files are PUT in the next sync The problem is that SyncJournalFileRecord::SyncJournalFileRecord will fail to get the inode after the forst move because the files are already moved on the filesystem. Normaly it should use the inode from the discovery phase in that case but that is not working because it comes from the remote node in case of moves, so the code in SyncEngine::treewalkFile would not set the inode. Test in https://github.com/owncloud/smashbox/pull/143		2016-01-20 13:49:12 +01:00
..
3rdparty	OS X: Fix alignment of "Copy" button in protocol #4207	2016-01-04 16:16:15 +01:00
cmd	owncloudcmd: Don't do a check that file are older than 2s (#4160)	2015-11-20 15:16:09 +01:00
crashreporter	cmd and crashreporter minor typos	2015-09-10 17:34:26 +05:45
gui	Sharing: Allow only one share dialog per path #3184	2016-01-20 13:17:54 +01:00
libsync	SyncEngine: fix inode after move if the file has moved on the file system	2016-01-20 13:49:12 +01:00
CMakeLists.txt	Force linkage against libc++	2015-07-02 13:31:25 +02:00