From: Sasha Levin <sashal@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, kees@kernel.org, hch@infradead.org,
broonie@kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.12-rc5
Date: Tue, 22 Oct 2024 17:20:59 -0400 [thread overview]
Message-ID: <ZxgXO_uhxhZYtuRZ@sashalap> (raw)
In-Reply-To: <20241022204931.GL21836@frogsfrogsfrogs>
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
next prev parent reply other threads:[~2024-10-22 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 17:39 Kent Overstreet
2024-10-22 19:06 ` Sasha Levin
2024-10-22 19:30 ` Kees Cook
2024-10-22 19:34 ` Mark Brown
2024-10-23 11:39 ` Sasha Levin
2024-10-22 20:49 ` Darrick J. Wong
2024-10-22 21:20 ` Sasha Levin [this message]
2024-10-23 10:42 ` Michael Ellerman
2024-10-23 11:41 ` Sasha Levin
2024-10-24 22:19 ` Kent Overstreet
2024-10-22 22:58 ` Kent Overstreet
2024-10-24 20:33 ` pr-tracker-bot
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=ZxgXO_uhxhZYtuRZ@sashalap \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=kees@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®