On Wed, Apr 02, 2025 at 09:34:18PM +0200, Remo Senekowitsch wrote: > Mailing lists don't suffer from this as much, because mail clients don't go > out of their way to hide old patchset versions from users. However, they also > don't provide any tools to help code reviewers associate old and new versions > of patchsets. A change-id header could be essential in developing tooling > for mailing lists that track patchsets and even individual patches within > them across versions. Easily being able to view the interdiff between the > last-reviewed version of a patchset and its most recent version is tremendously > useful for any code review workflow. Yes, this already exists, using change-id footers. E.g. you can run this inside your git checkout: $ b4 diff 20250331-b4-pks-collect-build-fixes-v2-0-6b06136808f3@xxxxxx Grabbing thread from lore.kernel.org/all/20250331-b4-pks-collect-build-fixes-v2-0-6b06136808f3@xxxxxx/t.mbox.gz Checking for older revisions Grabbing search results from lore.kernel.org --- Analyzing 19 messages in the thread Preparing fake-am for v1: meson: fix handling of '-Dcurl=auto' range: 98f2b1fb3587..163b98dec916 Preparing fake-am for v2: meson: fix handling of '-Dcurl=auto' range: 1406ab7e183b..df3c15fbd1ce --- Diffing v1 and v2 Running: git range-diff 98f2b1fb3587..163b98dec916 1406ab7e183b..df3c15fbd1ce --- 1: 6587b42aec = 1: f41c06addd meson: fix handling of '-Dcurl=auto' 2: d8d124b84d = 2: 8c2301bcd5 gitweb: fix generation of "gitweb.js" 3: 1f27a035f9 < -: ---------- meson: require Perl when building docs 4: 163b98dec9 = 3: e1962003a5 meson: respect 'tests' build option in contrib -: ---------- > 4: 6f07c417a8 meson: distinguish build and target host binaries -: ---------- > 5: df3c15fbd1 ci: use Visual Studio for win+meson job on GitHub Workflows -K
