Which are good modern version control systems (VCS)?

cracauer@ said:
As I said, that isn't more or less likely than on independently published source code.

You generally can't block scrapers from accessing source because you need things like ports to be able to download it outside a web browser.
Click to expand...
Surprise, surprise, HTTP uses port 80, HTTPS uses port 443, all possible using browsers.
 
RetroComputingCollector said:
I mean, even good-old-CVS is sufficient for NetBSD and OpenBSD. In fact, even an OpenBSD developer stated that CVS is good enough for them and there is no reason to switch: https://cvs.afresh1.com/~andrew/o/why-cvs.html

I think that FreeBSD's switch to git was rather pointless. What problem did it solve? No-one seems to be able to give an answer. Also, it was basically an encouragement of GPLed code. SVN was under the ALv2. Git is under 'GPLv2
Click to expand...

My understanding is that OpenBSD hacked up CVS to do a few more tricks, such as atomic multi-file commits.

The FreeBSD move to git was unavoidable because svn sucks.
 
rbranco said:
On systems without ZFS I tend to track /etc with git: `cd /etc ; sudo git init . ; sudo chmod 700 .git ; sudo git add . ; sudo git commit -m init`

And then you can track any changes with `git diff` & `git status`.
Click to expand...

I love this. I typically use RCS though so I only track the files I edit. It's a great idea.
 
You must log in or register to reply here.
Back
Top