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

Re: first impressions to git

From
Linus Torvalds <torvalds@osdl.org>
Date
Sep 18, 2005, 22:29 UTC
Message-ID
<Pine.LNX.4.58.0509181526220.9106@g5.osdl.org>
In-Reply-To
<20050918221125.GD22391@pasky.or.cz>
On Mon, 19 Sep 2005, Petr Baudis wrote:
> 
> I think it should actually never happen, updating the references should
> always come as the last thing in the push (or pull, for that matter)
> process.
It happens when you have several layers of non-git-aware stuff in between.

On kernel.org it happens occasionally with the mirroring, for example. I push something out while a mirror event is active, and the mirroring ends up finding the refs before the objects.

The same could happen with a write-back distributed networked filesystem, for example (not NFS, which is synchronous in metadata, but some other level of non-git-aware thing that doesn't necessarily maintain write ordering).

In general, git does the right thing for anything that honors write ordering, but the fact is, there are things that don't.

		Linus
Previous: Junio C HamanoNext: Sven Verdoolaege
Message 10 of 11 in “first impressions to git”
  1. Nico -telmich- SchotteliusSep 18, 2005
  2. Petr BaudisSep 18, 2005
  3. Daniel BarkalowSep 18, 2005
  4. Junio C HamanoSep 18, 2005
  5. Nico -telmich- SchotteliusSep 18, 2005
  6. Kay SieversSep 18, 2005
  7. Junio C HamanoSep 18, 2005
  8. Petr BaudisSep 18, 2005
  9. Junio C HamanoSep 18, 2005
  10. Linus TorvaldsSep 18, 2005
  11. Sven VerdoolaegeSep 19, 2005

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.