u guessed right. im one of the world's few solo software developers left (behind).

Keep on keeping on brother.

thank you.

or using branches.

oh svn had branches. people just didn't know that they wanted a distributed cvs.

for me atomic commit or was that committing a bunch of files with 1 command was important. and cvs wouldnt let me do it. perforce did. but it was proprietary software, though i think they offered a free version for solo developers or something like that. and when svn came out i jumped ship.

The vast majority of git users are using github as a central repository. There a a few other not github but serves the same purpose central repositories. Distributed sounds cool, but almost everybody wouldn't notice a thing if git was centralized.

Yup, I guess local commits when GitHub is offline (as it is frequently) is a decent improvement on a central subversion server if you are genuinely working offline or your scan server is as faliable as saas tends to be.

I used subversion for 10 years and don’t ever recall a problem when it was offline but the killed feature of GitHub - distributed source control - proved too complex For the majority of development teams. Instead there’s a “main” which people fork, add a feature, then merge and delete the fork.