Simon McVittie wrote: > On Sat, 16 Aug 2025 at 14:58:56 -0700, Russ Allbery wrote: >> I agree that it's not quite as good as Gerrit at showing you deltas >> between arbitrary revisions of the patch > > ... Github, Gitlab, and the git data model in general don't really have any > concept of what is "a different revision of the same patch" - the only > information they have is an earlier version of the pull/merge request (a > base commit + a patch series), and a later version (base commit + patch > series again). Gerrit can identify that you think a commit is "the same" by > it keeping a previously-used Change-ID, but without enforcing that > information being present, Github and Gitlab can't know that you consider > two commits with very similar commit messages or very similar diffs to be > "the same thing". If you haven't used it before, the git range-diff command is very useful for comparing revisions of a patch series (or PR/MR/whatever names forges make up). The range-diff command shows changes to the code as well as the commit message, which is quite often what needs some adjustment during the review of a patch series. I don't know if either Github or Gitlab can show something similar to a range-diff. I _think_ they might be able to, but I don't use either of them enough to be sure. (That's partly because even when I'm submitting or reviewing something at either of them, I tend to fetch the changes locally and then use the git command line tools. But, I know that's not everyone's cup of tea.) -- Todd
Attachment:
signature.asc
Description: PGP signature