from Hacker News

WTF,Kees?

by ryannevius on 6/1/25, 9:08 AM with 9 comments

• by inejge on 6/1/25, 12:31 PM

  According to a recent message from Kees Cook, it was the "b4" tool that produced a mangled tree[1]. Try following the reflog: at that level, wrangling git is akin to juggling flaming live chainsaws.

  [1] https://lore.kernel.org/all/202505312300.95D7D917@keescook/

• by dooglius on 6/1/25, 11:05 AM

  Should have followed the tried and true approach of https://xkcd.com/1597/

  This sort of thing is how I will never understand the attitude of people who claim that git is not actually confusing and you just have to learn it. If even the titans of kernel development (for whom git was created!) get screwed up, what hope do the rest of us have?

• by vdupras on 6/1/25, 11:44 AM

  If Linus is correct in his assumption that malicious work has to be involved to produce this tree (rather than being the result of merges and rebases gone wrong), it would indicate that Kees' development machines are compromised.

• by netfortius on 6/1/25, 9:44 AM

  > "You need to nuke that tree, and come up with a good explanation for this kind of shit." ... > "Konstantin - please disable Kees' account immediately until this is cleared up"

  Could Kees really nuke that tree, if Konstantin disables his account?!?

• by chr1ss_code on 6/1/25, 12:53 PM

  I think this read deserves a more engaging title - for example 'WTF,Kees? - Kernel Maintainer Under Fire By Linus' :P