-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using existing cloned repository #20
Comments
Honestly, I'm not sure. I expect that git uses some lock to prevent data corruption in such scenario but I don't know if that happens. You'd need to do some research on that topic. |
Thanks for the answer, I did a quick google search but found nothing related. That said git is doing an impressive job to keep integrity, I never managed to corrupt any repositories until now. |
According to this comment http://stackoverflow.com/questions/750765/concurrency-in-a-git-repo-on-a-network-shared-folder/751026#751026 you should be rather safe. This one http://git.661346.n2.nabble.com/concurrent-fetches-to-update-same-mirror-td5893458.html is particularly about concurrent git fetches and it seems nothing wrong should happen. |
Nice findings, thanks for reporting them :) |
Hi,
I really like the idea of reusing my already cloned repository instead of cloning them again somewhere else but I was wondering how git would handle things in case of simultaneous operations, if git-dude is doing a fetch and at the same time I am doing a pull for example.
While I am pretty sure it may well never happen I would not want to corrupt a repository by accident.
Any idea if this case would be handled gracefully by git ?
The text was updated successfully, but these errors were encountered: