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

Re: Understanding Git Under The Hood: Trees

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 15, 2013, 17:31 UTC
Message-ID
<7vwqnmrhbw.fsf@alter.siamese.dyndns.org>
In-Reply-To
<520CCC53.4090308@op5.se>
Andreas Ericsson <ae@op5.se> writes:
> You seem to believe that the in-memory representation of trees have to
> be the same as the on-disk one. That's simply not true. Git cheats
> outrageously with internal formats for pretty much everything in order
> to squeeze out more performance.

While the last statement applies to other parts of the system, it is not true for the in-core index design. We always had a flat index, and it is not cheating at all. The original "tree" was also a flat representation of everything under the sun, and hierarchical tree objects came much later.

Previous: Andreas EricssonNext: Erik Bernoth
Message 3 of 6 in “Understanding Git Under The Hood: Trees”
  1. Erik BernothAug 15, 2013
  2. Andreas EricssonAug 15, 2013
  3. Junio C HamanoAug 15, 2013
  4. Erik BernothAug 15, 2013
  5. Andreas EricssonAug 16, 2013
  6. Erik BernothAug 16, 2013

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.