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

Re: Centralized processes in git

From
Steven Grimm <koreth@midwinter.com>
Date
Aug 21, 2007, 00:40 UTC
Message-ID
<46CA3485.4080207@midwinter.com>
In-Reply-To
<46CA3398.9060803@midwinter.com>
Steven Grimm wrote:
> the repository-altering commands would grab a shared lock.

I guess that's a bit confusing -- what I mean to say is that the repository-altering commands that today do not lock the repository would grab a shared lock such that, in the absence of something else grabbing the exclusive lock, they will continue to effectively not lock the repository. IOW, by grabbing the shared lock they will continue to exhibit their current behavior under normal conditions.

-Steve
Previous: Steven GrimmNext: Jeff King
Message 4 of 5 in “Centralized processes in git”
  1. Robert BooneAug 20, 2007
  2. Jan HudecAug 20, 2007
  3. Steven GrimmAug 21, 2007
  4. Steven GrimmAug 21, 2007
  5. Jeff KingAug 21, 2007

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.