All of lore.kernel.org
 help / color / mirror / Atom feed
From: gang.yan@linux.dev
To: mptcp@lists.linux.dev
Subject: Re: [RFC] Mitigating Sashiko-driven iteration noise on the main MPTCP list
Date: Thu, 03 Sep 2026 06:22:43 +0000	[thread overview]
Message-ID: <2e771c1355c7d5d3faf42feed55ced63bc5869cb@linux.dev> (raw)
In-Reply-To: <b13525eb141d18e1fe326fec4e71b53704cdc291@linux.dev>

September 3, 2026 at 2:12 PM, gang.yan@linux.dev mailto:gang.yan@linux.dev  wrote:

> 
>  I believe both sides will benefit clearly if the sashiko process is mitigated:
> 
>  1. For reviewers/maintainers: Their main list inbox will only contain two types of patches—brand new
>  submissions (v1) and "mature" patches that have already passed the bot's checks. This drastically
>  reduces noise and allows them to focus their limited reviewing bandwidth on patches that are truly
>  ready for human scrutiny.
>  2. For contributors: They can iterate as fast and as often as they want in the sub‑list without feeling
>  guilty about flooding the main list. They get a "safe sandbox" to polish the series until it meets
>  the bot's criteria. When they finally post to the main list, the patch is already in a much better
>  state, which should also speed up the human review process.
> 

Having said that, I realize this might be an overdesign. If anyone else is bothered by the sashiko process
in a similar way, please leave messages under this thread, maybe we can find a lighter approach.

> I want to stress that this is not a complaint or a demand. I fully respect the work that has gone into
> Sashiko and the current process.
> 
> Looking forward to hearing everyone's thoughts.
> 
> Thanks
> Gang
>

  reply	other threads:[~2026-09-03  6:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  6:12 [RFC] Mitigating Sashiko-driven iteration noise on the main MPTCP list gang.yan
2026-09-03  6:22 ` gang.yan [this message]
2026-09-03  9:52 ` Matthieu Baerts
2026-09-04  7:25   ` gang.yan
2026-09-04 10:32     ` Matthieu Baerts
2026-09-07 12:57       ` Shardul Bankar
2026-09-07 13:47         ` Matthieu Baerts
2026-09-10 11:08         ` gang.yan
2026-09-11  9:58           ` Matthieu Baerts

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=2e771c1355c7d5d3faf42feed55ced63bc5869cb@linux.dev \
    --to=gang.yan@linux.dev \
    --cc=mptcp@lists.linux.dev \
    /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.