Conversation

Notices

1. Embed this notice
   iced depresso (icedquinn@blob.cat)'s status on Thursday, 21-Nov-2024 23:03:45 JST iced depresso
   > refusing to update the filesystem because the head dev behind it was a meanie
   
   god damn linux is fucked
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Thursday, 21-Nov-2024 23:04:52 JST iced depresso

     in reply to

     • casey is remote
     @realcaseyrollins linus told the bcachefs guy they weren't accepting any more pull requests because the cock team's panties are in a knot
   • Embed this notice
     casey is remote (realcaseyrollins@noauthority.social)'s status on Thursday, 21-Nov-2024 23:04:53 JST casey is remote

     in reply to

     @icedquinn Wait what? What's this?

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Thursday, 21-Nov-2024 23:16:27 JST iced depresso

     in reply to

     • casey is remote
     @realcaseyrollins they don't remove things once shipped, generally, because that would break the system.
     
     it does put them in a very awkward situation of shipping something outdated and incompatible because everyone involved is having a hissyfit
   • Embed this notice
     casey is remote (realcaseyrollins@noauthority.social)'s status on Thursday, 21-Nov-2024 23:16:28 JST casey is remote

     in reply to

     @icedquinn I just looked it up and holy heck yeah that's warranted lol

     Removing #bcachefs from #Linux entirely actually doesn't sound like a terrible idea

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Thursday, 21-Nov-2024 23:17:35 JST iced depresso

     in reply to

     • casey is remote
     @realcaseyrollins the problem is largely that linus is being a little bitch hiding behind beurocracy and bcache man is being a retard not accepting how the release schedule works and nobody is actually interested in keeping the goddamn system functioning