From: Roman Gushchin <roman.gushchin@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"Luck, Tony" <tony.luck@intel.com>,
"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: How to credit Sashiko with a Reported-by tag?
Date: Sat, 05 Sep 2026 15:51:55 -0700 [thread overview]
Message-ID: <87h5k3nwfo.fsf@linux.dev> (raw)
In-Reply-To: <20260904184904.7c62db0868ccb7d86fac3fea@linux-foundation.org> (Andrew Morton's message of "Fri, 4 Sep 2026 18:49:04 -0700")
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
prev parent reply other threads:[~2026-09-05 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 16:57 How to credit Sashiko with a Reported-by tag? Luck, Tony
2026-09-04 17:26 ` Steven Rostedt
2026-09-04 20:18 ` Linus Torvalds
2026-09-05 1:49 ` Andrew Morton
2026-09-05 22:51 ` Roman Gushchin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h5k3nwfo.fsf@linux.dev \
--to=roman.gushchin@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=ksummit@lists.linux.dev \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.