Bootstrap operation from hell [1]

[1] - https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23...

Thanks for the link... I've never read the README before, and it's very entertaining. Now I'm going to have "goddamn idiotic truckload of sh*t" echoing through my head all day

I read, when the project was introduced, but forgotten it a long time ago. Goddamn Idiotic Truckload of Sh*t Hub, Inc. would make a memorable name for an incorporation.

Also, the source of git would also reveal a problem when examined. To get around that one starts hypothesizing the sort of globe-spanning conspiracy against which one might as well give up ("well, maybe all my compilers (not just gcc, all of them) are also backdoored to backdoor themselves, and each other if you cross-compile, then backdoor git too...").

This summer: One man looked too deeply into the source code of his compilers and didn't like what he found.

Quickly, damon_c! To Kickstarter!

The kernel hasn't always been tracked in git though. How would we know something wasn't added before the source was imported into git?

Because before it was tracked by git, it was in bitkeeper, and it was likely in some other system before that.

I understand that. But what I don't know are the capabilities of those other, older systems that once tracked the kernel source. Do we have the same assurances there?

Great question.

BitKeeper wasnt as good as git when it comes to changesets and introducing bugs, still it was founded on more social side of changes needing approvals. Before that it was CVS and for that its almost easy to introduce backdoors.