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

Curious about details of optimization of object database...

From
Cchris@seberino.org <chris@seberino.org>
Date
Jan 9, 2009, 17:46 UTC
Message-ID
<20090109174623.GC12552@seberino.org>

I'm told a commit is *not* a patch (diff), but, rather a copy of the entire tree.

Can anyone say, in a few sentences, how git avoids needing to keep multiple slightly different copies of entire files without just storing lots of patches/diffs?

cs
Next: Matthieu Moy
Message 1 of 5 in “Curious about details of optimization of object database...”
  1. chris@seberino.orgJan 9, 2009
  2. Matthieu MoyJan 9, 2009
  3. Nicolas PitreJan 9, 2009
  4. David BrownJan 9, 2009
  5. Boyd Stephen Smith Jr.Jan 9, 2009

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.