clarification on "racy-git" & very fast change+commit

[David Tweed <tweed314@yahoo.co.uk>]

Hi, I'm getting prepared to do a trial migration my "selected files chronological database"
(think plan9's venti but not on every single file) to git and I'd just like to check something.

I'm still don't understand lots of stuff about git but I've read "racy-git.txt" in
Documentation for git-1.4.4.2. It appears to be saying that there used to be a race (involving
1-second timestamp limitations of filesystems) but now
things are done with a slow path fallback for would-race situations so that there is no race in
any operations any more? If the race is there, the file suggests it isn't a problem
for commiting?

I'm just checking because the way I'm planning to migrate is by using a script to
loop, checking out each snapshot from my existing backup system and commit it into git. I've got
quite a fast PC with a reasonable amount of memory but using ext3 as filesystem (which
still has 1 second timestamp resolution AIUI),
so it seems entirely plausible that I could get checkouts which alter only a few files
taking much, much less than a second. I don't know if any of them also happen to
have the same filesize, if they do this pattern seems more likely to meet the condtions of the
"race" than natural, normal git usage, so I want to see if I need to think about this dealing
with this issue. My understanding from racy-git.txt is that I don't.

Many thanks for any insight,

cheers, dave tweed





		
___________________________________________________________ 
Try the all-new Yahoo! Mail. "The New Version is radically easier to use" – The Wall Street Journal