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

Re: 'read-tree -m head' vs 'read-tree head'

From
Junio C Hamano <junkio@cox.net>
Date
May 3, 2005, 19:13 UTC
Message-ID
<7vbr7sw2aj.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20050503124935.GT25004@cip.informatik.uni-erlangen.de>

The form "git-read-tree <tree>" does not care what the original cache contained and builds the cache from scratch. On the other hand, "git-read-tree -m <tree>" uses what the original cache contained to speed things up in later checkout-cache. That's the official version of difference description.

That said, I've been wondering if "git-read-tree -m <tree>" always does the same thing (but only making the operation afterwards faster) as "git-read-tree <tree>". That is, if there is a valid use case where you would want to use it without "-m" because "-m" does something wrong. If there is no such valid use case probably we should always do "-m" version if we are reading only one tree, practically deprecating "-m" flag to the same status as "-r" flag to git-diff-cache.

However, I have not had time to think things through and have not bugged Linus about it myself.

Previous: Thomas GlanzmannNext: Petr Baudis
Message 2 of 5 in “'read-tree -m head' vs 'read-tree head'”
  1. Thomas GlanzmannMay 3, 2005
  2. Junio C HamanoMay 3, 2005
  3. Petr BaudisMay 3, 2005
  4. Junio C HamanoMay 4, 2005
  5. Thomas GlanzmannMay 4, 2005

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.