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

Re: Check for differents trees

From
Junio C Hamano <junkio@cox.net>
Date
Nov 6, 2005, 18:09 UTC
Message-ID
<7vy841y7fl.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20051106153830.18963.qmail@web26312.mail.ukl.yahoo.com>
Marco Costalba <mcostalba@yahoo.it> writes:
Show 12 quoted lines
> What I use now is:
>
> git-diff-tree -r --name-status sha1 sha2
>
> An then I parse the output for 'A' or 'D' as first char of
> each line. When I found one of that two chars I kwnow trees
> have different files set.
>
> The problem is that if sha1 and sha2 correspond to very
> "distant" revision the output of git-diff-tree can be very
> long and also usless as long as I stop searching at first
> match.
Perhaps
	$ git-diff-tree -r --name-status --diff-filter=AD sha1 sha2

would help you somewhat? This would not make the diff generation part quicker, but at least you do not have to parse other types of changes.

Previous: Marco CostalbaNext: Johannes Schindelin
Message 2 of 3 in “Check for differents trees”
  1. Marco CostalbaNov 6, 2005
  2. Junio C HamanoNov 6, 2005
  3. Johannes SchindelinNov 6, 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.