Hacker News new | ask | show | jobs
by inejge 378 days ago
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/

1 comments

Specifically the "b4 trailers" command, somehow. I don't have any special knowledge of b4, but it sounds as if a command that was expected to rewrite only the history of an under-review feature branch accidentally reached back too far and rewrote some of Kees' copy of master — without leaving a hint in the "Committer" field as it was conventionally supposed to.

Linus (rightly-ish) objected to this confusing breach of convention and did the contributor equivalent of a "revert quickly, debug at leisure." Kees (rightly) dug into the puzzle, figured out the problem, and explained it to Linus's (or at least Konstantin's) satisfaction.

https://b4.docs.kernel.org/en/latest/contributor/trailers.ht...