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

Re: git format-patch --range-diff bug?

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 12, 2020, 17:57 UTC
Message-ID
<xmqqk0uqjw4l.fsf@gitster.c.googlers.com>
In-Reply-To
<20201112174353.GD4270@szeder.dev>
SZEDER Gábor <szeder.dev@gmail.com> writes:
Show 5 quoted lines
> 	: The output of the range-diff command is what I would expect to be included in the generated patch &&
> 	git range-diff v1...v2 &&
>
> 	: But that is not what we get embedded in the generated patch &&
> 	git format-patch -1 --range-diff=v1...v2 v2 &&
The other day I did something similar and ended up with
	git format-patch --range-diff=v1 v1..v2

Would it help not to use the three-dot form? From my reading of "git format-patch --range-diff=<previous>" description, it only needs to give a single range (i.e. previous side of series of commits) as the other range to be compared are by definition the patches you are producing, while v1...v2 syntax is to give two ranges with one option. So...

Previous: SZEDER GáborNext: Eric Sunshine
Message 2 of 5 in “git format-patch --range-diff bug?”
  1. SZEDER GáborNov 12, 2020
  2. Junio C HamanoNov 12, 2020
  3. Eric SunshineNov 12, 2020
  4. Junio C HamanoNov 12, 2020
  5. Eric SunshineNov 12, 2020

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.