Re: Sashiko email policy precedence
Miguel Ojeda <[email protected]> Wed, 10 Jun 2026 07:57:10 +0200
| Newsgroups | dev.linux.lists.sashiko |
|---|---|
| Message-ID | <CANiq72kVXwvAfhkjpiZ6SooHXT+dSn1=nwTJ-SU2Tej2+JZgBw@mail.gmail.com> |
On Tue, Jun 9, 2026 at 7:21=E2=80=AFPM Roman Gushchin <roman.gushchin@linux= .dev> wrote: > > Very vague idea at this point, but: for each patchset sashiko can > determine the main MAINTAINERS entry it covers and apply it's rules. > That would help with the case when large mailing lists are cc'ed. > Now if e.g. a patchset is sent to e.g. bpf@ and netdev@, sashiko > tries to find a combination of the rules and it's kinda tricky... > Maybe the better approach is to decide which subsystem is primary here, > e.g. by the subject prefix or diff stat, and go with the corresponding > rules. Thanks for clarifying! Yeah, finding somehow the "main" entry would work well in most cases, though it will still be ambiguous in certain cases of course. If you mean using an LLM to determine what is the "main" one (since you already have spent tokens reading the series into context) and then using that as input for an algorithm that decides (still taking into account wide lists etc.), then it could work fairly well. I guess -- people may prefer a "fully deterministic" approach though. Cheers, Miguel