There are a couple things fallacious in changes.rst. Issues are
inaccurate language (patch 1). Patch 2 adds toolsets and patch 3 updates
the list in the translations. Finally patch 4 is a preview for a way to
handle the marking of optional software.

---
->[v2]
Ditch the name change [PATCH 1/5 v1]
Add Acked-by: Randy Dunlap to [PATCH 1/4 v2], [PATCH 2/4 v2]
Add genisoimage, mtools and syslinux to list [PATCH 2/4 v2]
Ditch footnotes in favor of a column [PATCH 4/4 v2]

[v1]
 https://lore.kernel.org/all/20260812120805.1631430-3-manuelebnerli@mailbox.org/
---

On Mon, Aug 31, 2026 at 5:17 PM Manuel Ebner <manuelebnerli@mailbox.org> wrote:
>
> ->[v2]
> Ditch the name change [PATCH 1/5 v1]
> Add Acked-by: Randy Dunlap to [PATCH 1/4 v2], [PATCH 2/4 v2]
> Add genisoimage, mtools and syslinux to list [PATCH 2/4 v2]
> Ditch footnotes in favor of a column [PATCH 4/4 v2]
>
> [v1]
>  https://lore.kernel.org/all/20260812120805.1631430-3-manuelebnerli@mailbox.org/

In my usual go-through-the-ML exercise, I noticed that the subjects of
these emails look a bit strange: one is missing the version, the
version is at the end, and they seem to be out of order:

  https://lore.kernel.org/all/20260831151605.638172-2-manuelebnerli@mailbox.org/

I would suggest using `-vN` in `git-format-patch` or `b4` to handle
this instead.

In addition, if the changes on a given version are local to each
patch, you may add them per patch instead, after the `---` line, if
that makes it easier to track.

I hope that helps.

Cheers,
Miguel