3 ms·
You'd be surprised how many people still use CVS.
by eli 17y ago
You'd be surprised how many people still use CVS.
- pavel_lishin 17y agoYou'd be surprised by how many don't use any kind of CVS.
- ryanwaggoner 17y agoI'm actually not surprised, and I've worked on plenty of client projects where the "workflow" was to login via FTP and edit live files on the server. If there was a chance for a potential conflict, just yell across the room to the other developer to make sure you don't step on each other. Sadly, a few of these were for large interactive agencies. I try and steer clear of these kinds of jobs when I can, or at least try and push them towards svn or git.
- briancooley 17y agoI worked for a client that used this exact method, plus comments in the source to indicate who changed the code, with old code commented out. I was one of several developers working remotely. It was a mess. When I suggested version control, the reply was "We're not big enough." Sigh.
- AndrewDucker 17y agoYup, my employers are still standardised on CVS. We're hoping to start trying out SVN in the next year or so - but Git is just too different to gain any traction in the near future. Not helped by the fact that SVN has hooks into the Visual Studio version control architecture, whereas Git has an odd plugin that works in a non-standard way.
- umjames 17y agoYep, my employer still uses CVS, and by "uses" I really mean blindly commits everything (including output files) using TortoiseCVS with no commit messages. No branches, almost no tags. I mentioned git once to my boss and it was definitely over his head. So I put git (via Cygwin) on my machine and am using it with CVS (as much as I can).
- spudlyo 17y agoYou'd be surprised how many people still use RCS. I've recently learned RCS so I could make changes to files managed by Foswiki, a modern and quite nice Wiki.