Am 12.02.2015 um 20:48 schrieb Junio C Hamano:
> Karsten Blees <karsten.blees@xxxxxxxxx> writes:
>
>> However, some users have expressed concerns that 'same size and
>> mtime' [2] may theoretically happen by chance in daily operation.
>
> Hmph.
>
> Haven't we already accepted that it is not just "may theoretically
> happen" and had counter-measures in racy-git detection machinery
> for quite some time?
>
Racy-git only triggers for files that are modified at the same time
as .git/index (i.e. we don't know if the stat cache is up to date).
This is more about copying 'old' things around, which usually also
copies mtime on Windows. E.g.:
# create two files with slightly different mtime
for i in {1..10}; do (echo "v1" >> test); done &&
for i in {1..10}; do (echo "v2" >> test2); done
# wait a bit so that '.git/index' is always newer than 'test' / 'test2'
sleep 1
git add test
git commit -m v1
# copy test2 over test (similar to 'cp -p', but native 'copy' also
# copies mtime nanoseconds)
cmd //c "copy /y test2 test"
git add test
git commit -m v2
Without these patches, git does not detect the change, and the second
git add / git commit are noops.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html