From: James Lawrence <jalexanderlawrence@gmail.com>
To: kent.overstreet@linux.dev
Cc: admin@aquinas.su, gbcox@bzb.us, jalexanderlawrence@gmail.com,
josef@toxicpanda.com, linux-bcachefs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
list-bcachefs@carlthompson.net, malte.schroeder@tnxip.de,
sashal@kernel.org, torvalds@linux-foundation.org, tytso@mit.edu
Subject: Peanut gallery 2c
Date: Mon, 11 Aug 2025 13:00:07 -0400 [thread overview]
Message-ID: <20250811170007.646981-1-james@egdaemon.com> (raw)
In-Reply-To: <ct5pqur2cwn2gulxuu277uomoknflxae32zzpyf4yqbrxcxj4d@p5j77u6xks4l>
fair enough, I was less explicit about which are which. btrfs has mostly a branding issue at this stage, which is fairly rough to dig out of.
You would know better than I would since you're directly in the weeds. I only have prior experiences and old cases to go off, of most of which are out dated at this point, and im primarily interested in raid 5/6 usecases.
Which is why I've mostly stayed out of the lkml drama until now. But removal doesnt resolve the problems with the linux filesystem ecosystem
and it'd be a disservice to everyone to lose convienent access to the work you've done.
crossing my fingers your work will remain,
James Lawrence
Principal Engineer
next prev parent reply other threads:[~2025-08-11 17:00 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 15:14 [GIT PULL] bcachefs changes for 6.17 Kent Overstreet
2025-08-05 21:19 ` Malte Schröder
2025-08-05 22:41 ` Carl E. Thompson
2025-08-07 12:42 ` Aquinas Admin
2025-08-09 17:36 ` Kent Overstreet
2025-08-09 19:21 ` Josef Bacik
2025-08-09 20:37 ` Kent Overstreet
2025-08-09 21:34 ` Kent Overstreet
2025-08-10 2:24 ` Theodore Ts'o
2025-08-10 3:17 ` Kent Overstreet
2025-08-10 4:05 ` Sasha Levin
2025-08-10 4:13 ` Kent Overstreet
2025-08-10 4:26 ` Gerald B. Cox
2025-08-10 5:17 ` Kent Overstreet
2025-08-10 5:59 ` Theodore Ts'o
2025-08-10 6:51 ` Kent Overstreet
2025-08-10 10:22 ` Martin Steigerwald
2025-08-11 15:48 ` Peanut gallery 2c James Lawrence
2025-08-11 16:08 ` Kent Overstreet
2025-08-11 17:00 ` James Lawrence [this message]
[not found] ` <aJsIOj6jbPKayO0s@mayhem.fritz.box>
2025-08-12 16:26 ` Kent Overstreet
2025-08-11 16:48 ` [GIT PULL] bcachefs changes for 6.17 Aquinas Admin
2025-08-10 8:02 ` Martin Steigerwald
2025-08-10 6:05 ` Carl E. Thompson
2025-08-11 16:02 ` Aquinas Admin
2025-08-11 16:09 ` Kent Overstreet
2025-08-09 23:01 ` Matthew Wilcox
2025-08-09 23:13 ` Kent Overstreet
2025-08-12 7:49 ` Jani Partanen
2025-08-12 10:09 ` Martin Steigerwald
2025-08-11 9:51 ` Konstantin Shelekhin
2025-08-11 14:26 ` Kent Overstreet
2025-08-11 18:13 ` Carl E. Thompson
2025-08-11 18:40 ` Malte Schröder
2025-08-12 0:44 ` Carl E. Thompson
2025-08-11 18:48 ` Aquinas Admin
2025-08-11 19:42 ` Martin Steigerwald
2025-08-11 21:04 ` Konstantin Shelekhin
2025-08-12 1:08 ` Kent Overstreet
2025-08-12 6:52 ` asdx
2025-08-12 7:04 ` Kent Overstreet
2025-08-12 7:17 ` asdx
2025-08-12 19:35 ` Keith Busch
2025-08-12 20:03 ` Kent Overstreet
2025-08-12 20:30 ` Keith Busch
2025-08-12 20:31 ` Kent Overstreet
2025-08-12 20:38 ` Keith Busch
2025-08-12 20:45 ` Kent Overstreet
2025-08-12 20:54 ` Keith Busch
2025-08-12 20:57 ` Kent Overstreet
2025-08-11 16:45 ` Aquinas Admin
2025-08-10 4:29 ` Gerhard Wiesinger
2025-08-07 14:27 ` Martin Steigerwald
2025-08-07 17:29 ` Peter Schneider
2025-08-10 6:20 ` Gerhard Wiesinger
2025-08-10 10:32 ` Martin Steigerwald
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=20250811170007.646981-1-james@egdaemon.com \
--to=jalexanderlawrence@gmail.com \
--cc=admin@aquinas.su \
--cc=gbcox@bzb.us \
--cc=josef@toxicpanda.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=list-bcachefs@carlthompson.net \
--cc=malte.schroeder@tnxip.de \
--cc=sashal@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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