Off the top off my head:
* Real renames (right now, it's implemented as a delete/add, but that will
be fixed at some point. Even at that, that's better than CVS's total lack
of support for that oP)
* Multiple access methods, webdav, file, ssh, etc
* Directory versioning
* No network access needed until a commit (or update) is asked for (more or
less. There are other cases where you'll need that, but the normal adds,
diffs, deletes, etc. all affect only the WC until you tell it to commit the
repo)
* Active development. I think some claim CVS is still under development,
but, come on. Really. :P
There are probably a lot more, but those are the only ones that come to mind
at the moment.
On 5/24/07, Priti Tiwary <Priti.Tiwary_at_sun.com> wrote:
>
> Hi,
> I have tried svn only once, but would like to know "Why SVN"?
> Can someone using svn for sometime, compare how its better than CVS?
> Priti
>
> Jason Lee wrote:
> > On 5/24/07, *Karam Singh Badesha* <Karam.Badesha_at_sun.com
> > <mailto:Karam.Badesha_at_sun.com>> wrote:
> >
> > We use svn extensively for all of CAD group inside SUN. So whatever
> I
> > can help with, I will. SVN is better than cvs, so its a good move.
> >
> >
> > I concur completely. SVN is MUCH better than CVS. :)
> >
> > --
> > Jason Lee, SCJP
> > JSF RI Dev Team
> > http://blogs.steeplesoft.com
>
> --
> Priti Tiwary
> Open ESB Community (http://open-esb.org)
>
--
Jason Lee, SCJP
JSF RI Dev Team
http://blogs.steeplesoft.com