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?


DK

On 8/6/06, Cameron Childress <[EMAIL PROTECTED]> wrote:
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 for CVS users:

Subversion for CVS Users:
http://svnbook.red-bean.com/en/1.0/apa.html

-Cameron

On 8/6/06, Douglas Knudsen < [EMAIL PROTECTED]> wrote:
> from my vantage as a CVS user, this begs the pregunta so to speak.  Just
> what did SVN give you that CVS didn't have?


-------------------------------------------------------------
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------






--
Douglas Knudsen
http://www.cubicleman.com
this is my signature, like it?
-------------------------------------------------------------
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by FusionLink
-------------------------------------------------------------

Reply via email to