Re: Maybe make Sashiko emails opt-in please?

["Danilo Krummrich" <dakr@kernel.org>]

On Fri Apr 24, 2026 at 12:16 AM CEST, Roman Gushchin wrote:
> I generally rely on maintainers for the decision how to use Sashiko or not use
> at all.

I think in practice, this doesn't work out. Regardless of how maintainers decide
for their subsystems, once another subsystem mailing list is involved things are
overwritten in one or the other way. This is especially true for mailing lists
such as the rust-for-linux one, which span across various subsystems.

My main concern with the current approach is that I'm worried that contributors
of the subsystems / components / drivers I maintain may immediately act on
feedback without discussing the validity of the feedback or the solution for the
problem with other people on the list first, when it is received as a private
message.

(Analogously, I would not like if for publically posted patches reviewers would
provide private feedback to the contributor.)

That said, I don't know what a solution would look like to actually make this a
maintainer decision; most likely it simply isn't possible and it has to be a
collective decision.

For me personally it would be fine if we could add a clear disclaimer upfront
that mentions that contributors should share when and how they plan to act on
the received feedback with all other recipients of the patch (series) before
acting on it (unless it is obviously trivial).

As for the opt-out, unless sashiko feedback is sent in a way that all recipients
of a patch can discuss it as necessary, any sashiko mails to me go straight into
the bin anyways, as I look things up on the website as necessary.

That said, I really like the tool and I think it provides very valuable feedback
-- thanks for working on this!

- Danilo