All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Jiri Kosina" <jikos@kernel.org>, <ksummit@lists.linux.dev>
Cc: <sashiko@lists.linux.dev>
Subject: Re: Patch pre-submission to Sashiko
Date: Sat, 17 Oct 2026 18:20:47 +0000	[thread overview]
Message-ID: <DM7BL6J0WCXU.1I38BKL4RJLFI@gmail.com> (raw)
In-Reply-To: <nn69829p-nn62-ppn7-968q-64o246ss90or@xreary.bet>

On Sat Oct 17, 2026 at 5:28 PM UTC, Jiri Kosina wrote:
>
> [ in the spirit of the concluding discussion at this year's maintainers 
>   summit,  I'm using this list outside of actual maintainer summit 
>   planning :) ]
>
> I have just received a v1 to v11 patchset submission within roughly one 
> day timeframe.
>
> Neither myself nor anyone else did comment with any review feedback, 
> except for Sashiko. Which I believe is what triggered all the immediate 
> resubmissions.
>
> I don't think this is sustanable.

I think it's just fine. I encourage developers to keep the spam going.

You can simulate github style squah of v1->v2->v3 in your inbox.
Ask your agent to monitor inbox, archive vN when vN+1 arrives
and summarize v1->vN discussion. Then you'll always have the latest
patch set to look at and a summary of what happened when you were away.
Then sit on it for a day or a week to see whether respin
cycle has ended (and bots stopped talking to each other) and then
do a human part of maintainership.


  parent reply	other threads:[~2026-10-17 18:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 17:28 Patch pre-submission to Sashiko Jiri Kosina
2026-10-17 18:02 ` Theodore Tso
2026-10-17 18:20 ` Alexei Starovoitov [this message]
2026-10-17 18:38   ` Arnaldo Melo
2026-10-18 11:46   ` Mark Brown
2026-10-17 18:20 ` Linus Torvalds
2026-10-17 20:10   ` Roman Gushchin
2026-10-18 13:41     ` Steven Rostedt
2026-10-18 18:41     ` Kees Cook
2026-10-18 18:58       ` Linus Torvalds
2026-10-17 19:42 ` Andrew Lunn
2026-10-18 11:54   ` Mark Brown
2026-10-18 16:48     ` Laurent Pinchart

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=DM7BL6J0WCXU.1I38BKL4RJLFI@gmail.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=jikos@kernel.org \
    --cc=ksummit@lists.linux.dev \
    --cc=sashiko@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.