diff --side-by-side v1.patch v2.patch
diff --side-by-side v1.patch v2.patch
Posted Apr 21, 2022 17:28 UTC (Thu) by mathstuf (subscriber, #69389)In reply to: diff --side-by-side v1.patch v2.patch by newren
Parent article: Git 2.36.0 released
Still waiting on forges to adopt this command's output for rebased MRs…
Posted Apr 21, 2022 17:59 UTC (Thu)
by marcH (subscriber, #57642)
[Link] (3 responses)
More background in the Gitlab feature request https://gitlab.com/gitlab-org/gitlab/-/issues/24096
Posted Apr 21, 2022 18:14 UTC (Thu)
by newren (subscriber, #5160)
[Link] (1 responses)
Also, the link you give for Gerrit seems to be for a single change. While you can do a range-diff for a single patch of a series, it's not quite the same thing. I did like the comparison of the current patch against older patchsets and used that in Gerrit, but I still I really would have liked something like range-diff in Gerrit back when I was still using it up to about 6 months ago. To my knowledge, it still doesn't exist in Gerrit.
Out of curiosity, was there something in the Git 2.36 release announcements that triggered this discussion about this feature from Git 2.19, or is this just an interesting tangent?
Posted Apr 21, 2022 19:55 UTC (Thu)
by mathstuf (subscriber, #69389)
[Link]
The GP was comparing the diff rendering changes to diffs-of-diffs.
Posted Apr 21, 2022 18:16 UTC (Thu)
by mathstuf (subscriber, #69389)
[Link]
> More background in the Gitlab feature request https://gitlab.com/gitlab-org/gitlab/-/issues/24096
Yeah, that's a visited link for me :) . One of my issues is even closed as a duplicate of this one.
diff --side-by-side v1.patch v2.patch
I think that was long before git itself had it.
diff --side-by-side v1.patch v2.patch
diff --side-by-side v1.patch v2.patch
diff --side-by-side v1.patch v2.patch