Re: Darcs-git: a few notes for Git hackers
- From
- Juliusz Chroboczek <juliusz.chroboczek@pps.jussieu.fr>
- Date
- May 9, 2005, 23:08 UTC
- Message-ID
- <7i3bsw0zhr.fsf@lanthane.pps.jussieu.fr>
- In-Reply-To
- <427FE938.7050904@zytor.com>
>> In such cases, manual intervention is necessary anyway -- a file could >> have been written half-way.
> In the case of git, it should not be necessary even then; there might > be a broken file in the repository but nothing would reference it so > it shouldn't have any effect. Functionally speaking, operations on > the git repository are in themselves atomic.
Yes, you're right.
I still prefer using a lockfile to flock -- NFS-safety is important for us. And experience with the Darcs user base (who are probably less Unix-savvy then the Git userbase) shows that they have no problem doing
$ ps $ rm _darcs/lock $ darcs check
when Darcs complains about a stray lockfile.
Juliusz