On Wed, Sep 06, 2023 at 12:36:18PM -0700, Linus Torvalds wrote: > So I'm starting to look at this because I have most other pull > requests done, and while I realize there's no universal support for it > I suspect any further changes are better done in-tree. The out-of-tree > thing has been done. > > However, while I'll continue to look at it in this form, I just > realized that it's completely unacceptable for one very obvious > reason: > > On Sat, 2 Sept 2023 at 20:26, Kent Overstreet <kent.overstreet@xxxxxxxxx> wrote: > > > > https://evilpiepirate.org/git/bcachefs.git bcachefs-for-upstream > > No way am I pulling that without a signed tag and a pgp key with a > chain of trust. You've been around for long enough that having such a > key shouldn't be a problem for you, so make it happen. > > There are a few other issues that I have with this, and Christoph did > mention a big one: it's not been in linux-next. I don't know why I > thought it had been, it's just such an obvious thing for any new "I > want this merged upstream" tree. > > So these kinds of "I'll just ignore _all_ basic rules" kinds of issues > do annoy me. > > I need to know that you understand that if you actually want this > upstream, you need to work with upstream. > > That very much means *NOT* continuing this "I'll just do it my way". > You need to show that you can work with others, that you can work > within the framework of upstream, and that not every single thread you > get into becomes an argument. > > This, btw, is not negotiable. If you feel uncomfortable with that > basic notion, you had better just continue doing development outside > the main kernel tree for another decade. > > The fact that I only now notice that you never submitted this to > linux-next is obviously on me. My bad. > > But at the same time it worries me that it might be a sign of you just > thinking that your way is special. > > Linus Honestly, though, this process is getting entirely kafkaesque. I've been spending the past month or two working laying the groundwork for putting together a team to work on this, because god knows we need fresh blood in filesystem land - but that's on hold. Getting blindsided by another three month delay hurts, but that's not even the main thing. The biggest thing has just been the non stop hostility and accusations - everything from "fracturing the community" too "ignoring all the rules" and my favorite, "is this the hill Kent wants to die on?" - when I'm just trying to get work done. I don't generally think of myself as being particularly difficult to work with, I get along fine with most of the filesystem developers I interact with - regularly sharing ideas back and forth with the XFS people - but these review discussions have been entirely dominated by the most divisive people in our community, and I'm being told it's entirely on me to work with the guy whos one constant in the past 15 years has been to try and block everything I submit? I'm just trying to get work done here. I'm not trying to ignore the rules. I'm trying to work with people who are willing to have reasonable discussions. ------------------- When I was a teenager, I wanted nothing more than to be a Linux kernel programmer. I thought it utterly amazing that this huge group of people from around the world were working together over the internet, and that anyone could take part if they had the chops. That was my escape from a shitty family situation and the assholes in my life. But my life is different now; I have new and better people in my life, and I have to be thinking about them, and if merging bcachefs means I have to spend a lot more time in interactions like this then it's going to make me a shitty person to be around; and I don't want to do that to myself and I definitely don't want to do that to the people I care about. I'm going to go offline for awhile and think about what I want to do next.
