On Tue, Oct 22, 2024 at 01:49:31PM -0700, Darrick J. Wong wrote:
On Tue, Oct 22, 2024 at 03:06:38PM -0400, Sasha Levin wrote:
other information that would be useful?
As a maintainer I probably would've found this to be annoying, but with
all my other outside observer / participant hats on, I think it's very
good to have a bot to expose maintainers not following the process.
This was my thinking too. Maybe it makes sense for the bot to shut up if
things look good (i.e. >N days in stable, everything on the mailing
list). Or maybe just a simple "LGTM" or a "Reviewed-by:..."?
Commits that weren't found on lore.kernel.org/all:
--------------------
e04ee8608914d bcachefs: Mark more errors as AUTOFIX
f0d3302073e60 bcachefs: Workaround for kvmalloc() not supporting > INT_MAX allocations
bc6d2d10418e1 bcachefs: fsck: Improve hash_check_key()
dc96656b20eb6 bcachefs: bch2_hash_set_or_get_in_snapshot()
15a3836c8ed7b bcachefs: Repair mismatches in inode hash seed, type
d8e879377ffb3 bcachefs: Add hash seed, type to inode_to_text()
78cf0ae636a55 bcachefs: INODE_STR_HASH() for bch_inode_unpacked
b96f8cd3870a1 bcachefs: Run in-kernel offline fsck without ratelimit errors
4007bbb203a0c bcachefS: ec: fix data type on stripe deletion
Especially since there were already two whole roarings about this!
This was a very good demonstration!
PS: Would you be willing to share the part that searches lore? There's
a few other git.kernel.org repos that might be interesting.
It's all at https://git.kernel.org/pub/scm/linux/kernel/git/sashal/next-analysis.git/
In particular, the query-lore.sh script.
--
Thanks,
Sasha
