Post AveGteMRtvovwtR7x2 by buonhobo@fosstodon.org
 (DIR) More posts by buonhobo@fosstodon.org
 (DIR) Post #AveCMl4ZWipfOM8RmK by BrodieOnLinux@mstdn.social
       2025-06-30T06:19:30Z
       
       0 likes, 0 repeats
       
       Say what you will about angry Linus, but have you ever seen defeated Linus https://lore.kernel.org/all/CAHk-=wi+k8E4kWR8c-nREP0+EA4D+=rz5j0Hdk3N6cWgfE03-Q@mail.gmail.com/
       
 (DIR) Post #AveCw15BzgDBBJEoEq by jsbarretto@social.coop
       2025-06-30T06:25:49Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux Gotta catch em all
       
 (DIR) Post #AveDtC5Oj9QoOQYHRY by waltercool@pl.slash.cl
       2025-06-30T06:36:35.637998Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux The answer:
       
 (DIR) Post #AveE64PAb3PAKpwL3I by fabiscafe@mstdn.social
       2025-06-30T06:38:54Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux and Kent's answer to it. In my opinion he shouldn't be involved in upstream Linux
       
 (DIR) Post #AveE8xXsYZjJvgOJyi by BrodieOnLinux@mstdn.social
       2025-06-30T06:39:27Z
       
       1 likes, 0 repeats
       
       @fabiscafe Linus has threatened to pull the project at least 3 times now, so we'll see if it happens this time
       
 (DIR) Post #AveGteMRtvovwtR7x2 by buonhobo@fosstodon.org
       2025-06-30T07:10:16Z
       
       0 likes, 0 repeats
       
       @BrodieOnLinux @fabiscafe The best solution imho is to have Kent develop bcachefs on his own, and he could either ship it as a dkms or have a second contributor (one who can follow basic rules, unlike him) tasked with upstreaming the changes to the kernel.Either way, Kent should not interact directly with the kernel anymore since he proved he's not capable