4 ms·
If you want to version control a single file locally with no fuss (exactly one file,v file for storing changesets), I could still see it being handy. It seems
by Erwin 13y ago
If you want to version control a single file locally with no fuss (exactly one file,v file for storing changesets), I could still see it being handy.
It seems it has a maintainer that is very inclusive and accepts all portability fixes. Which is nice enough; many newer open source products are more like fireflies.
- adfadf 13y agoRCS is still used at my work. Some of its features (or omission of features) work well with our shared file system, and we often need to keep only one or two files in a directory under version control.
- pjungwir 13y agoI worked at an agency around 2000-2005 that used RCS to keep files like httpd.conf under source control. Not a great solution, but there were no free "configuration management" tools then, and it was a pretty unrestricted place, with developers and sysadmins sharing access to production systems. It's not what I'd do today, but it was better than nothing and gave them some safety without costing much in process.
- _ak 13y agoOne of my previous employers still uses CVS to version and deploy configuration. One reason why git is not an option is the simple fact that you can't check out subdirectories in git.
- jessaustin 13y agoIf one were using git, why would one need to check out a directory? I have no objection to people using the tools they prefer, but they should be honest with themselves. The barrier to using git while working in a particular directory lies in changing one's VCS habits, not in a deficiency in git.