I like to keep mine razor sharp. Sharp enough you can shave with it. Why I’ve been known to circumcise a gnat.
I like to keep mine razor sharp. Sharp enough you can shave with it. Why I’ve been known to circumcise a gnat.
The “stormy shits” in parts of Atlantic Canada.
Bought a new computer, threw the old one out.
Use etc-keeper, saves everything in a git repo and integrates with a bunch of package managers. Been using it for decades it feels like now.
Exit codes from processes are damage points that you take against your HP. When your HP runs out, the distro reformats itself to a clean state.
I don’t know man, speaking as someone who lives in a hurricane-heavy locale we have to deal with broken windows due to storms with some regularity.
Watched this over the Christmas break. The best review I had read from someone else was from a post on Lemmy that said something to the effect of “if you set up a TV to play 10 generic sci-fi movies and just changed the channel between them allrandomly you’d end up with a film as cohesive as Rebel Moon.”
Apparently a season 4 too which I was unaware of. There are places you can read, but I’ll refrain from posting, but they wouldn’t be difficult to find if you take a look around.
Did you read the comic continuation? There’s an official season 3 in comic book form.
Linus wrote git to be used via email as part of its core design, so that was just the way he rolled back then. GitHub and Gitlab and all the cloud platforms and tooling came afterwards and it took time to reach a critical mass, and even then, some folks stick to what they’re used to.
Looking at Linus’ GitHub profile, looks like not much has changed — 100% commits, 0% everything else.
Also not Linus from the Peanuts comic.
Not sure. He’s a KGB-educated Russian billionaire oligarch so take from that what you will.
It was literally Eugene Kaspersky, founder and CEO of Kaspersky.
One other thing you may have to do if you have contributors who have also committed code is to get their permission to change the license as well, as the code they committed may still be under their copyright and not yours, and they can choose to allow their code to be relicensed or not. Some projects use a contributor release to reassign copyright for contributions for reasons like this, for instance. This is partly the reason why the Linux kernel has never changed to GPLv3 and still uses GPLv2 (and also because Linus just doesn’t like some provisions of the GPLv3) — it would be pretty much impossible to get everyone who contributed code to a project as large as the kernel to agree to a license change. Any code that couldn’t be changed would need to be extracted and rewritten, and that’s not going to happen given the sheer size of the code base.
If you don’t have other contributors then you’re home free. You can’t retroactively change licenses to existing copies of the code that have been distributed, but you can change it going forward.