That's right, Linus decides.

I honestly don't think there's anything wrong with the code. I've been a long-time user of the original bcache and it's been rock solid, so I'm sure you can totally pull it off with bcachefs - I've seen you do it before. Furthermore, I'm sure one can easily find a lot of lower quality work in the kernel right now if one decides to dig for it for some reason. I don't think that's really the problem.

Thing is, writing the code is one thing, but selling it to the public is an entirely different one. When I want to send a patch to some upstream project, and the patch itself is done, I always have this thought crossing my mind: "ok, the easy predictable part is done, now for the hard, unpredictable one". I then have to explain what this patch is, why it's necessary, how I tested it, how I tried to adhere to the project's existing best practices, and also make sure it's super simple to apply. When I do so, I try to put myself in the shoes of the person I'm addressing and imagine what they might think and what their objections might be. Oftentimes this goes smooth, but sometimes I have a really hard time and it simply goes nowhere. It's impossible to predict, really - you just have to keep a positive attitude and hope you can get your point across. When you see your pitch not working, trying to be flexible, finding other angles, better reasoning, adapting your work to the received feedback, iterate, etc etc. And hoping that eventually it works.

Yes, it sucks to have to prove to other people that your work is sound and your reasoning is right, especially when you *know* it is. Unfortunately, *they* often don't. They might also have their own limitations and flaws when it comes to communication. Ever been to a technical interview where you knew you could totally ace the job, but left the interviewer totally unconvinced? Unfortunately, winning over people is a completely different discipline, but a necessary one nonetheless.

> the way to solve it is with a conversation. I think the chances for that happening evaporated a long time ago.

I actually have a feeling that they didn't yet. Did you ask yourself why bcachefs wasn't removed in this -rc1? I keep thinking about this, and the only reason I see is because Linus doesn't really want to, so he waits for some reason not to. I think you can still give him that reason. Honestly, just writing the same thing you wrote here, about being tired and frustrated, being on edge, having to deal with non-technical issues, etc etc, and asking for a time-out for a release cycle to rethink the communication strategy, might just be enough. The only thing which would be absolutely necessary is to treat people with respect - we are all humans, we all have flaws, we're all struggling, and no one really knows how to solve this, so we have to try and be kind to one another in the process, even when nothing seems to work. And hope for the best.