SZEDER Gábor <szeder.dev@xxxxxxxxx> writes: > : 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...
