mmlb

I've had that same "what's the point" thought every time I've read about stacked PRs, but recently had an (obvious) epiphany. The benefit is you get CI for each commit! I've always hated fixup/typo/fix tests commits and toyed with having a CI check that enforced ci passing on each commit but this drops that need.

In this instance the PR that was merged was from 6 years ago and was clear https://github.com/pedronauck/reworm/pull/28. Looks to me like a force push overwrote the commit that now exists in history since it was done 6y later.

Use the lessons learned from those before us in less heterogeneous days, aka inspect the binaries you're going to call out to for fitness. Things like "check if grep is gnu or bsd" or "check if sl is sapling or steamlocomotive".

I've done that a bit to deal with macos crippled bash for example.

No script element zapper can remove it, easy peasy.

True, but I imagined fetching every file with wget or equivalent and then just using it locally. Doesn't work anyway because the data is not all there.

Ah I see now, I didn't traverse deep enough whem checking.

For bzr did you try archive.org? https://web.archive.org/web/20150321194412/https://code.liw....

You are right that he can't unilaterally relicense the kernel and that it will likely never happen, but Linus is in fact against the GPLv3, see debconf 14 Q&A: https://youtu.be/5PmHRSeA2c8?t=2840

I used to use DDD as a GUI frontend to GDB.

https://www.gnu.org/software/ddd/

The way I read GP, the python script can very well do the equivalent of gcc -DPARAM=42 -o binary-param=42 && ./binary-param-42.

edit: oh nm, reread GP...

I think puranjay interpreted the snippet as a joke referring to college students in fraternity as the "primates in a primate house".

virtual machines. For custom kernels, clusters, both, and other reasons. Having more than 1 vm running gets to be a pain with 8gigs or less.