From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Roman Gushchin <roman.gushchin@linux.dev>,
ackerleytng@google.com, akpm@linux-foundation.org,
chriscli@google.com, hannes@cmpxchg.org, harry@kernel.org,
jack@suse.cz, liam@infradead.org, muchun.song@linux.dev,
shakeelb@meta.com, sj@kernel.org, ziy@nvidia.com,
"Lorenzo Stoakes (Arm)" <ljs@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
SeongJae Park <sj@kernel.org>
Subject: Sashiko change proposal
Date: Thu, 15 Oct 2026 10:38:14 +0200 [thread overview]
Message-ID: <5eae44a6-06c3-445c-9508-58b372c01b2c@kernel.org> (raw)
(CCing all people attending the mm-next call)
Hi,
After talking to Roman at MS, he just informed me that sashiko now has a new
feature combination:
- "embargo_hours": hours before review is public + emails sent
- Mechanism for signed-in maintainers to lift embargo immediately
That solves the key issue I had with sashiko: people/agents re-spinning stuff
too fast before a human at least had the chance to jump in first.
I suggest the following sashiko change for linux-mm:
diff --git a/projects/linux/mailing_lists.toml b/projects/linux/mailing_lists.toml
index a9198de..ba123da 100644
--- a/projects/linux/mailing_lists.toml
+++ b/projects/linux/mailing_lists.toml
@@ -46,7 +46,6 @@ ignored_emails = ["patchwork@emeril.freedesktop.org"]
["linux-integrity@vger.kernel.org"]
["linux-kernel@vger.kernel.org"]
["linux-kselftest@vger.kernel.org"]
-["linux-mm@kvack.org"]
["linux-nvme@lists.infradead.org"]
["linux-omap@vger.kernel.org"]
["linux-pm@vger.kernel.org"]
@@ -315,3 +314,7 @@ reply_to = ["author", "list", "recipients"]
["fsverity@lists.linux.dev"]
reply_to = ["author", "list", "recipients"]
+
+["linux-mm@kvack.org"]
+reply_to = ["author", "list", "recipients"]
+embargo_hours = 24
Which means:
- Embargo 24h
- Mails sent to everybody (author, list, CC list)
- No positive-review ("looks great") mails (default)
- No other static email addresses that receive a copy (default)
- No additional ignored author email addresses (default)
I'd say we start with 24h and see how it goes.
Thoughts?
--
Cheers,
David
next reply other threads:[~2026-10-15 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 8:38 David Hildenbrand (Arm) [this message]
2026-10-15 8:46 ` Sashiko change proposal Lorenzo Stoakes (ARM)
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=5eae44a6-06c3-445c-9508-58b372c01b2c@kernel.org \
--to=david@kernel.org \
--cc=ackerleytng@google.com \
--cc=akpm@linux-foundation.org \
--cc=chriscli@google.com \
--cc=hannes@cmpxchg.org \
--cc=harry@kernel.org \
--cc=jack@suse.cz \
--cc=liam@infradead.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=shakeelb@meta.com \
--cc=sj@kernel.org \
--cc=vbabka@kernel.org \
--cc=willy@infradead.org \
--cc=ziy@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox