←back to thread

145 points ksec | 1 comments | | HN request time: 0.239s | source
Show context
dralley ◴[] No.44466224[source]
I donate to Kent's patreon and I'm very enthusiastic about bcachefs.

However, Kent, if you read this: please just settle down and follow the rules. Quit deliberately antagonizing Linus. The constant drama is incredibly offputting. Don't jeopardize the entire future of bcachefs over the silliest and most temporary concerns.

If you absolutely must argue about some rule or other, then make that argument without having your opening move be to blatantly violate them and then complain when people call you out.

You were the one who wanted into the kernel despite many suggestions that it was too early. That comes with tradeoffs. You need to figure out how to live with that, at least for a year or two. Stop making your self-imposed problems everyone else's problems.

replies(3): >>44467229 #>>44467347 #>>44468804 #
NewJazz ◴[] No.44467229[source]
Seriously how hard is it to say "I'm unhappy users won't have access to this data recovery option but will postpone its inclusion until the next merge window". Yeah, maybe it sucks for users who want the new option or what have you, but like you said it is a temporary concern.
replies(1): >>44467698 #
vbezhenar ◴[] No.44467698[source]
Why does it suck for users? Those brave enough to use new filesystem, surely can use custom kernel for the time being, while merge effort is underway and vanilla kernel might not be the most stable option.
replies(1): >>44471139 #
cwillu ◴[] No.44471139[source]
I believe part of the problem is distributions including it in their installers without requiring any of the usual “type the words “I KNOW WHAT I'M DOING”” to proceed” warning gates that are otherwise typical.
replies(3): >>44472095 #>>44472344 #>>44477863 #
1. int_19h ◴[] No.44477863[source]
By this logic it should be kept out of the kernel entirely until it's stable enough for general use.