Anatoly Borodin writes:
> It's not like `git diff X^2 X` is a big problem, but too much of a
> copypaste.
Brace expansion helps a bit: git diff X{^2,}
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for someth
Hi!
Jeff King wrote:
> For the first one, showing all diffs is what I want. For the second, it
> only makes sense to for the first parent case, as following other
> parents would zig-zag through history.
Lucky you! :) You probably don't need to inspect 9 month old ex-svn
branches with sync (i.e.
Jeff King writes:
> On Sun, Mar 27, 2016 at 08:46:02PM +, Anatoly Borodin wrote:
>
>> is there a good reason for `git show -m` to not accept the number of a
>> parent of a merge commit? I can run `git show --first-parent COMMIT`,
>> but need to write `git diff COMMIT^2 COMMIT` every time I wa
On Sun, Mar 27, 2016 at 08:46:02PM +, Anatoly Borodin wrote:
> is there a good reason for `git show -m` to not accept the number of a
> parent of a merge commit? I can run `git show --first-parent COMMIT`,
> but need to write `git diff COMMIT^2 COMMIT` every time I want to diff
> with the seco
Hi All,
is there a good reason for `git show -m` to not accept the number of a
parent of a merge commit? I can run `git show --first-parent COMMIT`,
but need to write `git diff COMMIT^2 COMMIT` every time I want to diff
with the second parent!
`git cherry-pick -m 2 COMMIT` works, so why can't `g
5 matches
Mail list logo
