From: Nathan Owens <ndowens08@proton.me>
To: Kent Overstreet <kent.overstreet@linux.dev>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.11-rc5
Date: Fri, 06 Sep 2024 07:50:46 +0000 [thread overview]
Message-ID: <01252d3a-1856-4e9e-a395-3f15c0a3afd0@proton.me> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1880 bytes --]
Will say both Linus and Kent has their points and reasoning, but I must
ask, Kent please stick with the guidelines of submitting fixes,
features, etc. I would like that Bcachefs to stay in the kernel and see
how well Bcachefs comes along in the future and when it has your
features and ideas. One day I would like to maybe switch from BTRFS to
Bcachefs when it gets more features and some of the things I would like
to be able to do, like restore from snapshot and eventually boot to
snapshots to restore a messed up system. If it gets taken out of the
tree, less people will know about it, nor likely take the trouble of
compiling a kernel for Bcachefs.
This comment is not bash either Linus or you Kent, but just a thought in
hopes that more people will possibly switch to it and encourage
production keeps happening as well.
On 8/23/24 10:10 PM, Kent Overstreet wrote:
> On Sat, Aug 24, 2024 at 10:57:55AM GMT, Linus Torvalds wrote:
>> On Sat, 24 Aug 2024 at 10:48, K
ent Overstreet <kent.overstreet@linux.dev> wrote:
>>> Sure, which is why I'm not sending you anything here that isn't a fix
>>> for a real issue.
>> Kent, bugs happen.
> I _know_.
>
> Look, filesystem development is as high stakes as it gets. Normal kernel
> development, you fuck up - you crash the machine, you lose some work,
> you reboot, people are annoyed but generally it's ok.
>
> In filesystem land, you can corrupt data and not find out about it until
> weeks later, or _worse_. I've got stories to give people literal
> nightmares. Hell, that stuff has fueled my own nightmares for years. You
> know how much grey my beard has now?
>
> Which is why I have spent many years of my life building a codebase and
> development process where I can work productively where I can not just
> catch but recover from pretty much any fuckup imaginable.
>
> Because peace of mind is priceless...
>
[-- Attachment #1.2: publickey - ndowens08@proton.me - 0x227C5078.asc --]
[-- Type: application/pgp-keys, Size: 701 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next reply other threads:[~2024-09-06 7:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 7:50 Nathan Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-23 18:54 [GIT PULL] bcachefs fixes for 6.11-rc5 Kent Overstreet
2024-08-24 1:23 ` Linus Torvalds
2024-08-24 2:13 ` Kent Overstreet
2024-08-24 2:25 ` Linus Torvalds
2024-08-24 2:33 ` Kent Overstreet
2024-08-24 2:35 ` Linus Torvalds
2024-08-24 2:40 ` Linus Torvalds
2024-08-24 2:59 ` Kent Overstreet
2024-08-24 4:22 ` Carl E. Thompson
2024-08-24 11:48 ` Kent Overstreet
2024-08-24 2:47 ` Kent Overstreet
2024-08-24 2:57 ` Linus Torvalds
2024-08-24 3:10 ` Kent Overstreet
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=01252d3a-1856-4e9e-a395-3f15c0a3afd0@proton.me \
--to=ndowens08@proton.me \
--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;
as well as URLs for NNTP newsgroup(s).