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

Re: [PATCH 4/4 v6] cache-tree: Write updated cache-tree after commit

From
David Turner <dturner@twopensource.com>
Date
Jul 11, 2014, 23:37 UTC
Message-ID
<1405121841.3775.31.camel@stross>
In-Reply-To
<xmqq38e76gfi.fsf@gitster.dls.corp.google.com>
On Fri, 2014-07-11 at 08:52 -0700, Junio C Hamano wrote:
Show 8 quoted lines
> David Turner <dturner@twopensource.com> writes:
> 
> > @@ -16,8 +16,34 @@ cmp_cache_tree () {
> >  # We don't bother with actually checking the SHA1:
> >  # test-dump-cache-tree already verifies that all existing data is
> >  # correct.
> 
> Is this statement now stale and needs to be removed?

I think it is still accurate; we still don't bother to check SHAs and test-dump-cache-tree still does the comparison.

Previous: Junio C Hamano
Message 12 of 12 in “cache-tree: Create/update cache-tree on checkout”
  1. 1/4 cache-tree: Create/update cache-tree on checkoutDavid Turner, Jul 11, 2014
  2. 2/4 test-dump-cache-tree: invalid trees are not errorsDavid Turner, Jul 11, 2014
  3. 3/4 cache-tree: subdirectory testsDavid Turner, Jul 11, 2014
  4. Eric SunshineJul 11, 2014
  5. Junio C HamanoJul 11, 2014
  6. Junio C HamanoJul 11, 2014
  7. David TurnerJul 11, 2014
  8. Junio C HamanoJul 13, 2014
  9. David TurnerJul 11, 2014
  10. 4/4 cache-tree: Write updated cache-tree after commitDavid Turner, Jul 11, 2014
  11. Junio C HamanoJul 11, 2014
  12. David TurnerJul 11, 2014

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.