In today’s news: man with zero self reflection goes on lengthy one sided rant highlighting just that.
=> More informations about this toot | More toots from axboe@fosstodon.org
@axboe Gotta love that stray bullet toward block...
=> More informations about this toot | More toots from mathieu@fosstodon.org
@mathieu if I rolled my eyes any harder, they’d disappear out the back of my head.
=> More informations about this toot | More toots from axboe@fosstodon.org
@axboe I think I've missed something.
=> More informations about this toot | More toots from larsmb@mastodon.online
@larsmb you can read the latest posts from @kernellogger . But I recommend you skip clicking on the links for your own sanity.
=> More informations about this toot | More toots from Aissen@treehouse.systems
@axboe yea just from the intro, lots of disengenous and unnecessary framing, followed by complaining about it being hard to change a maintainer's mind but characterizing it as a failure of the CoC process, while repeatedly throwing shade at other contributors and the code they produce.
I honestly can't stomach trying to read the whole thing. I haven't gotten to anything remotely related to the CoC process and he's firmly convinced me that he's in the wrong.
=> More informations about this toot | More toots from kevingranade@tech.lgbt
@kevingranade throwing shade is a common theme. Not sure how many emails I’ve seen with Kent dumping on btrfs, seemingly as a way to prop up his own thing.
=> More informations about this toot | More toots from axboe@fosstodon.org
@axboe my take is more that this is a damning failure in leadership by Linus, the TAB and the kernel's CoC team
it's been clear for a year that there's a loose canon on deck, and it is still not yet tied down
=> More informations about this toot | More toots from sima@chaos.social
@axboe I'd expect that when this is all done, if this ever gets there because there's so many ways the current process can be torpedoed and dragged through the mudd, the reputational damage to CoC enforcement is going to be bigger than anything else that actually happened
=> More informations about this toot | More toots from sima@chaos.social
@sima @axboe i think it's a bit sad that mr. zero self reflection apparently doesn't understand how well is he being treated.
in my experience, most people respond to shit behaviour by simply withdrawing. he, on the contrary, got told exactly what is the issue, sometimes in an exceedingly kind manner (hello mr. bacik). giving him every chance of to improve, and it's a tragedy that he doesn't seem to realize that
=> More informations about this toot | More toots from lkundrak@metalhead.club
@lkundrak @axboe I wouldn't call it explaining in exceedingly kind manner, but enabling toxic behavior
there's a place for such kind explanations, but in private, and after you've taken measures to protect the community at large. after, not before
=> More informations about this toot | More toots from sima@chaos.social
@lkundrak @sima I actually rewatched that lsfmm session he claims got totally hijacked, and seems like nonsense to me. People suggested better alternatives to their current solution, which is what development is all about, and he refused to listen to any of it. Their solution was already perfect. Which is clearly nonsense, what Rostedt suggested is a much better approach than a bunch of macros. Just not willing to listen, he always knows best.
=> More informations about this toot | More toots from axboe@fosstodon.org
@axboe @lkundrak @sima Well now going through the allocation functions with lsp is pure joy. not.
=> More informations about this toot | More toots from mathieu@fosstodon.org This content has been proxied by September (ba2dc).Proxy Information
text/gemini