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

Re: [PATCH] cache-tree: populate cache-tree on successful merge

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 28, 2015, 19:55 UTC
Message-ID
<xmqq6154dpkt.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1438113266.18134.26.camel@twopensource.com>
David Turner <dturner@twopensource.com> writes:
> The work done to produce the cache-tree is work that the commit would
> otherwise have to do.  So we're spending extra time in one place to
> eliminate that work in a different place.
Good point.  Thanks.
Previous: David TurnerNext: Junio C Hamano
Message 4 of 10 in “cache-tree: populate cache-tree on successful merge”
  1. cache-tree: populate cache-tree on successful mergeDavid Turner, Jul 28, 2015
  2. Junio C HamanoJul 28, 2015
  3. David TurnerJul 28, 2015
  4. Junio C HamanoJul 28, 2015
  5. Junio C HamanoJul 28, 2015
  6. David TurnerJul 28, 2015
  7. Junio C HamanoJul 28, 2015
  8. Junio C HamanoJul 28, 2015
  9. David TurnerJul 28, 2015
  10. Junio C HamanoJul 28, 2015

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.