git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-cvsserver & push/commit atomically

From
Randal L. Schwartz <merlyn@stonehenge.com>
Date
Feb 13, 2006, 02:25 UTC
Message-ID
<86wtg0j8qr.fsf@blue.stonehenge.com>
In-Reply-To
<Pine.LNX.4.63.0602130110590.21465@wbgn013.biozentrum.uni-wuerzburg.de>
>>>>> "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!
Previous: Johannes Schindelin
Message 3 of 3 in “git-cvsserver & push/commit atomically”
  1. Martin LanghoffFeb 12, 2006
  2. Johannes SchindelinFeb 13, 2006
  3. Randal L. SchwartzFeb 13, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.