So he wanted features merged outside maintenance window again? I'm a bit inclined to think, Kent doesn't really want to play by the rules at all
The problem is linus here. The only time he should give a shit is if he has a technical problem with the code or it reaches outside of the bcachefs tree. And afiak neither case applies here. Its entirely process related.
Who's Kent?
I still don't understand why something so unstable and far from ready had to be put into the kernel upstream. How did Kent manage that? Is he really that good with words? Reading his messages on LKML, it really doesn't seem so. No-one is a god programmer, but was his code so convincing, his practices so good, his testing so thorough, that it being unstable could be ignored?
Its stable enough. Ive been running it almost 9 months now without issue through multiple kernel upgrades. Most of what kent is working on is the code for robust error correction.
A community for posting memes relating to linux!
Also check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
