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

Re: [PATCH 0/4] Revisiting cache-tree

From
Alex Riesen <raa.lkml@gmail.com>
Date
Apr 20, 2009, 13:08 UTC
Message-ID
<81b0412b0904200608r7b986160p15ec0afb826ee1f6@mail.gmail.com>
In-Reply-To
<1240225100-29960-1-git-send-email-gitster@pobox.com>
2009/4/20 Junio C Hamano <gitster@pobox.com>:
Show 16 quoted lines
> This series consists of a fix meant for maint branch, and two performance
> fix.  The second one is a refactoring of the code to support the latter.
>
> I was doing a rather huge import as a multi-step process by doing
> something like this:
>
>        $ rm -f $GIT_DIR/index
>        $ git add some ;# this one is huge
>        $ git tag one $(git write-tree)
>        $ git repack -a -d
>        $ rm -f $GIT_DIR/index
>        $ git add other ;# this one is also huge
>        $ git tag two $(git write-tree)
>        $ git repack -a -d
>
>        $ git read-tree some other
"git read-tree one two"
Previous: Junio C Hamano
Message 6 of 6 in “Revisiting cache-tree”
  1. 0/4 Revisiting cache-treeJunio C Hamano, Apr 20, 2009
  2. 1/4 read-tree A B: do not corrupt cache-treeJunio C Hamano, Apr 20, 2009
  3. 2/4 Move prime_cache_tree() to cache-tree.cJunio C Hamano, Apr 20, 2009
  4. 3/4 read-tree -m A B: prime cache-tree from the switched-to treeJunio C Hamano, Apr 20, 2009
  5. 4/4 checkout branch: prime cache-tree fullyJunio C Hamano, Apr 20, 2009
  6. Alex RiesenApr 20, 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.