SVN was an attempt to build a better CVS, so in the developers'
eyes, it solves all the shortcoming of CVS. In reality, most of the
differences have to do with how it handles versions, which also
impacts branching and merging. There's an appendix to the SVN book
that explains the differences
On 8/6/06, Douglas Knudsen [EMAIL PROTECTED] wrote:
righto. So, in a team of 10 developers that don't seem to run into these
'issues' in CVS that SVN solves, it doesn't seem very economical to go
through changing, eh?
All things held equal, I'm always a proponent of using the tools your
team
And a good book of exploration (which also discusses the differences and
benefits over CVS) is Pragmatic Version Control with Subversion, which I
have obtained from the publisher and am one chapter from finishing and then
will write up a review. Someone else had asked me at the meeting about
