Re: [PATCH 2/2] agents: add a skill to determine Fixes tags

[Thorsten Leemhuis]

On 10/9/26 00:54, Sasha Levin wrote:
>
> +A ``Fixes:`` tag identifies the commit that introduced the bug being fixed. [...]

Sorry for partly hijacking this, but it seems appropriate while we are
at it:

What exactly is the right commit to specify when it comes to a
regression caused by a change that exposed a way older bug? The change
that exposed it? The change that introduced it in the first place? Both?
I'd tend to "both", but I guess some people might consider this as too
noisy.

I've seen occasional discussions about this and our docs for humans are
a bit vague here:

Documentation/process/submitting-patches.rst says:
""If your patch fixes a bug in a specific commit, e.g. you found an
issue using git bisect, please use the ‘Fixes:’ tag with at least the
first 12 characters of the SHA-1 ID, and the one line summary.
[...]
A Fixes: tag indicates that the patch fixes a bug in a previous commit.
It is used to make it easy to determine where an issue originated""

And Documentation/process/5.Posting.rst says:
""One tag is used to refer to earlier commits which introduced problems
fixed by the patch:""

Ciao, Thorsten