Home » Mailing list archives » git » 2006 » February » 12

Re: git-cvsserver & push/commit atomically

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Randal L. Schwartz
Subject: Re: git-cvsserver & push/commit atomically
Date: Sunday, February 12, 2006 - 7:25 pm

>>>>> "Johannes" == Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Johannes> Correct. The filesystem way to lock is to create a lock file and
Johannes> fail if it already exists.

Unless NFS has been fixed, that's not an atomic operation over NFS.  Might not
matter here, but important to note if this is your first time seeing this lock
strategy.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
git-cvsserver &amp; push/commit atomically, Martin Langhoff, (Sun Feb 12, 4:50 pm)
Re: git-cvsserver &amp; push/commit atomically, Johannes Schindelin, (Sun Feb 12, 5:17 pm)
Re: git-cvsserver & push/commit atomically, Randal L. Schwartz, (Sun Feb 12, 7:25 pm)