Hi! testcase2.sh:
I found a case where fsvs 1.0.15 misses a change which was correctly recognized by fsvs 1.0.14. A test case script is attached. In this test case, the working copy moves and is resynchronized via sync-repos. A file in the moved working copy has been changed before. fsvs 1.0.15 misses the update of "Datei2" and the last line of the script returns "Datei2" instead of "Datei3" which would be correct. The "fsvs status" after the sync-repos shows that fsvs incorrectly thinks that the working copy is in sync. Additionally I have a further question: Without the "sleep", fsvs misses the update completely, as the file's mtime doesn't change. If you know it, it's obvious, and it's a case which should rarely happen in a production system, but I was still a bit surprised when it happened first. testcase6.sh: Here, the working copy is recreated at the same place, with the same content. fsvs works correctly, but shows all file's meta-data to be changed. Why does that happen, and is this correct? Both fsvs 1.0.14 and 1.0.15 commit the correct changes. Greetings, Gunter PS: For anyone who's interested: Both of my ignore-Pattern-patch apply flawlessly against fsvs 1.0.15, though with offsets and fuzz. I didn't commit them to fsvs as the ignore pattern format is likely to change anyway and I wanted to avoid two semantical changes of the ignore patterns in a short period of time. -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ "It would seem that you have no useful skill or talent whatsoever," he said. "Have you thought of going into teaching?" -- (Terry Pratchett, Mort) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + PGP-verschlüsselte Mails bevorzugt! + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
testcase2.sh
Description: application/shellscript
testcase6.sh
Description: application/shellscript
pgpilBiql7uOs.pgp
Description: PGP signature
