Re: Replacing Link trailers

[Steven Rostedt <rostedt@goodmis.org>]

On Mon, 13 Oct 2025 08:25:01 -0400
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:

> AFAIU. this use of Link trailer is used as a strategy to work around
> the lack of unique identifier in patch commit messages that identifies
> multiple revisions of a patch, for tracking by patch review tooling
> and facilitate digging through patch history.

That's not how I use it at all. Copying my reply from the tooling thread
here:

  [..]

So it allows you to not only find the cover letter of a series, but also
daisy chains all the links to previous versions so you can see how the
patch was developed, and all the comments to the older versions.

Now my workflow incorporates these link tags. When I need to create a new
version of the patch, I save the old git branch with its version:

  git branch topic-v1
  git reset --hard <base-commit>

Then I download the old version from patchwork, run my scripts to pull it
in (which adds the links to the emails of those commits). And when I make the
next version, I record the changes by replacing the:

  Link: https://lore.kernel.org/...

With

  Changes since v1: https://lore.kernel.org/...

And before sending my emails, I move that text below the '---'.

And this makes it very easy to incorporate the daisy chain. If I have to
use any external tooling to search for it, I'm not going to bother, and
this workflow will just stop happening.

-- Steve