How to credit Sashiko with a Reported-by tag?

How to credit Sashiko with a Reported-by tag?

[Luck, Tony]

I see 30 different variations so far. Most popular are:

    211     Reported-by: Sashiko <sashiko-bot@kernel.org>
    142     Reported-by: sashiko-bot <sashiko-bot@kernel.org>

which maybe make sense for those lists where a bot is sending e-mails to the list
though I think that ought to be accompanied with a Link: tag to the actual e-mail
and scanning a few of these commits it isn't done consistently.

Different e-mail addresses in tags where one has been used. Is there an official one?

  <sashiko-bot@kernel.org>
  <sashiko-dev@google.com>
  <sashiko@linuxfoundation.org>
  <sashiko@sashiko.dev>

But if there wasn't an e-mail? I see a handful of links to the reports on the sashiko.dev website:

      1     Reported-by: https://sashiko.dev/#/patchset/20260415143735.2974230-1-elver%40google.com
      1     Reported-by: https://sashiko.dev/#/patchset/20260424100221.32407-1-icheng%40nvidia.com
      1     Reported-by: https://sashiko.dev/#/patchset/20260521021249.3258069-1-oss%40fourdim.xyz

That looks most useful. Though perhaps I'd be concerned about the long-term durability of those links.

No consistency on whether to grant Sashiko a capital letter as befits a proper noun.

-Tony

Re: How to credit Sashiko with a Reported-by tag?

[Steven Rostedt]

On Fri, 4 Sep 2026 16:57:33 +0000
"Luck, Tony" <tony.luck@intel.com> wrote:

> I see 30 different variations so far. Most popular are:
> 
>     211     Reported-by: Sashiko <sashiko-bot@kernel.org>
>     142     Reported-by: sashiko-bot <sashiko-bot@kernel.org>
> 
> which maybe make sense for those lists where a bot is sending e-mails to the list
> though I think that ought to be accompanied with a Link: tag to the actual e-mail
> and scanning a few of these commits it isn't done consistently.
> 
> Different e-mail addresses in tags where one has been used. Is there an official one?
> 
>   <sashiko-bot@kernel.org>
>   <sashiko-dev@google.com>
>   <sashiko@linuxfoundation.org>
>   <sashiko@sashiko.dev>
> 
> But if there wasn't an e-mail? I see a handful of links to the reports on the sashiko.dev website:
> 
>       1     Reported-by: https://sashiko.dev/#/patchset/20260415143735.2974230-1-elver%40google.com
>       1     Reported-by: https://sashiko.dev/#/patchset/20260424100221.32407-1-icheng%40nvidia.com
>       1     Reported-by: https://sashiko.dev/#/patchset/20260521021249.3258069-1-oss%40fourdim.xyz
> 
> That looks most useful. Though perhaps I'd be concerned about the long-term durability of those links.
> 
> No consistency on whether to grant Sashiko a capital letter as befits a proper noun.

I treat the reports no different than anyone else sending me a bug report.
I use the email that sent it, and the Closes: tag to the email that
reported it.

For example:

    Reported-by: sashiko-bot@kernel.org
    Closes: https://lore.kernel.org/all/20260901164836.D962D1F000E9@smtp.kernel.org/

-- Steve

Re: How to credit Sashiko with a Reported-by tag?

[Linus Torvalds]

On Fri, 4 Sept 2026 at 11:27, Luck, Tony <tony.luck@intel.com> wrote:
>
> I see 30 different variations so far. Most popular are:
>
>     211     Reported-by: Sashiko <sashiko-bot@kernel.org>
>     142     Reported-by: sashiko-bot <sashiko-bot@kernel.org>

You missed a few other variations:

    Link: https://sashiko.dev/#/patchset/...

or

    Closes: https://sashiko.dev/#/patchset/...

which are sometimes - but certainly not always - accompanied by
Reported-by lines.

And quite a few times I've seen Sashiko mentioned just in the
free-form prose section.

Honestly, I don't think it matters which pattern ends up being used.
It's not like the bot is going to be upset about the different
spellings, so all that matters is that people see "oh, Sashiko did
something here".

           Linus

Re: How to credit Sashiko with a Reported-by tag?

[Andrew Morton]

On Fri, 4 Sep 2026 13:18:35 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Fri, 4 Sept 2026 at 11:27, Luck, Tony <tony.luck@intel.com> wrote:
> >
> > I see 30 different variations so far. Most popular are:
> >
> >     211     Reported-by: Sashiko <sashiko-bot@kernel.org>
> >     142     Reported-by: sashiko-bot <sashiko-bot@kernel.org>
> 
> You missed a few other variations:
> 
>     Link: https://sashiko.dev/#/patchset/...
> 
> or
> 
>     Closes: https://sashiko.dev/#/patchset/...
> 
> which are sometimes - but certainly not always - accompanied by
> Reported-by lines.
> 
> And quite a few times I've seen Sashiko mentioned just in the
> free-form prose section.
> 
> Honestly, I don't think it matters which pattern ends up being used.
> It's not like the bot is going to be upset about the different
> spellings, so all that matters is that people see "oh, Sashiko did
> something here".

There are people (Roman is one) who trawl the commit logs to get an
understanding of how effective/useful Sashiko is being.

I expect that some standardization in how changelogs reference Sashiko
might help in this work.  Roman?


(Last I checked, nearly 1000 commits mention Sashiko.  God that's a lot
of bugs we either fixed or didn't add!)

(And nice statistics for this will perhaps help persuade Google to keep
funding the thing)

Re: How to credit Sashiko with a Reported-by tag?

[Roman Gushchin]

Andrew Morton <akpm@linux-foundation.org> writes:

> On Fri, 4 Sep 2026 13:18:35 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>> On Fri, 4 Sept 2026 at 11:27, Luck, Tony <tony.luck@intel.com> wrote:
>> >
>> > I see 30 different variations so far. Most popular are:
>> >
>> >     211     Reported-by: Sashiko <sashiko-bot@kernel.org>
>> >     142     Reported-by: sashiko-bot <sashiko-bot@kernel.org>
>> 
>> You missed a few other variations:
>> 
>>     Link: https://sashiko.dev/#/patchset/...
>> 
>> or
>> 
>>     Closes: https://sashiko.dev/#/patchset/...
>> 
>> which are sometimes - but certainly not always - accompanied by
>> Reported-by lines.
>> 
>> And quite a few times I've seen Sashiko mentioned just in the
>> free-form prose section.
>> 
>> Honestly, I don't think it matters which pattern ends up being used.
>> It's not like the bot is going to be upset about the different
>> spellings, so all that matters is that people see "oh, Sashiko did
>> something here".
>
> There are people (Roman is one) who trawl the commit logs to get an
> understanding of how effective/useful Sashiko is being.
>
> I expect that some standardization in how changelogs reference Sashiko
> might help in this work.  Roman?
>
>
> (Last I checked, nearly 1000 commits mention Sashiko.  God that's a lot
> of bugs we either fixed or didn't add!)

1300+ as of now, but those are mostly pre-existing bugs in the codebase,
not bugs which are prevented, it must be a larger number. Prevented issues
are often mentioned in patchsets changelogs (e.g. v3: fixed X, Y and Z
[Sashiko]), but dropped before merging.

> (And nice statistics for this will perhaps help persuade Google to keep
> funding the thing)

I'd love to have a more accurate number of prevented issues to better
characterize the value for google and potential other sponsors, but it
doesn't seem to be realistic, partially because there are many
individual and corporate instances of sashiko being used.

In terms of a specific format of commit log, I agree with Linus, it
doesn't really matter. Luckily Sashiko seems to be quite a unique letter
combination, so grep'ping is really easy.

Thanks