Proof: what are the other source management softwares? (Don’t mention Mercurial, that’s cheating).
Also for Linux, it’s down to the license and history. Linux isn’t a bad investment because all commits directly to the kernel are given freely to all. And it’s not Unix. It doesn’t have the stain of AT&T and their sue happy ways. Also Linux dominates all computer markets except for user desktops. Servers, phones, application specific utilities, etc.
I actually miss SVN. It had a lot of issues, yes, but the cognitive barrier was so much smaller. When I have a merge error in git, I basically just delete my repo and make a new one…
It is also the version control system that uses sqlite which is pretty cool as far as disk space and resiliency are concerned esp. as compared to Git.
I don’t however like that it prides itself on not having any history rewriting features because I am kind of a fan of those. I like keeping embarrassing mistakes like a typo’d commit message or missing file out of my permanent commit history.
A bad standard adds to the pile.
A good standard crushes the pile.
Example: Git and Linux.
Proof: what are the other source management softwares? (Don’t mention Mercurial, that’s cheating).
Also for Linux, it’s down to the license and history. Linux isn’t a bad investment because all commits directly to the kernel are given freely to all. And it’s not Unix. It doesn’t have the stain of AT&T and their sue happy ways. Also Linux dominates all computer markets except for user desktops. Servers, phones, application specific utilities, etc.
Fossil, GNU Bazaar, SVN, as well as some other lesser known ones
I actually miss SVN. It had a lot of issues, yes, but the cognitive barrier was so much smaller. When I have a merge error in git, I basically just delete my repo and make a new one…
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
SVN, and whatever that thing Microsoft was doing once
Also, CVS, cvsup, both of which I’ve used in my early Linux years.
And fossil – which is the revision control system sqlite uses and I kind of like :)
It is also the version control system that uses sqlite which is pretty cool as far as disk space and resiliency are concerned esp. as compared to Git.
I don’t however like that it prides itself on not having any history rewriting features because I am kind of a fan of those. I like keeping embarrassing mistakes like a typo’d commit message or missing file out of my permanent commit history.
TFVS
Also RCS which I am basically obligated to mention