Bruce Hoult

Ok sure git config would work. Replacing any previous "rebased with history" (etc) line would be a better option than the current default, but I still personally prefer nothing at...

I really really really really want to see this functionality! I'm happy to have the test that is run be a script. Yes, I'll write it specifically for this purpose!...

One more thing. It is unfortunately the case that a merge that succeeds textually can fail more extensive tests (compilation, running a test suite) because of a bad commit in...

Here's an interesting example I hit just now. Commit https://github.com/llvm-project/llvm-project-20170507/commit/52b1e2e91ee removed a virtual function called enableMultipleCopyHints() from a header file and all implementations of it from various back ends. Our...

That commit definitely exists, and is over a year old: https://github.com/sifive/buildroot/tree/dfc15319532373fb8cea6b67edfd7f16c366d188 palmer-dabbelt Add tyrquake, an open source quake 1 implementation Latest commit dfc1531 on 14 Dec 2017

Ah yes. It seems git in general allows you do specify --depth from any branch, but not from a commit. That's maybe a little inconsistent as a branch is nothing...

> Most ARM64 CPUs also support ARMv7 instruction set for vackwards compartibility. Fewer and fewer. Apple's A11 and later SoCs (2017 iPhone 8 and on) don't. Many server CPUs such...

That would certainly be more natural for me, but I'm not American :-) Or "over 3000m"

If you use 32 bits (!!) for tags or sparse address space, 96 bits still needs a diamond 1.9m in diameter under the same assumptions. OK, so it could be...

Wild and crazy idea... Instead of having some binary encoded "number of 16 bit packets" field in the *next* (2nd) 16 bit packet ... what about if 1111xxxxx1111111 means the...