[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: SVN vs. AccuRev?

From: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Wed, 28 Jan 2009 15:46:34 -0000

I have to agree there - I evaluated AccuRev, and we would have bought it
if the credit crunch hadn't happened. The GUI tools are significantly
better than SVN at tracking branches, I think this is something that
should be taken to the TortoiseSVN list instead though, a good 'freeform
tree' branch/merge GUI would be a very welcome addition.

SVN itself could do more to hide the branches from the user, instead of
making the user branch into what are effectively new directories in the
repository tree, those directories could be hidden so the user has a
more transparent view of what branches are available - instead of
switching to a new directory, they'd switch to a named branch instead,
even though SVN internally would be unchanged. That's not much of a
criticism though.

I'm not convinced the merge tools themselves are much better on Accurev,
SVN merging now is quite good.

-----Original Message-----
From: Jorge M [mailto:jmedina_at_e-dialog.com]
Sent: Wednesday, January 28, 2009 2:17 PM
To: users_at_subversion.tigris.org
Subject: RE: SVN vs. AccuRev?

I have used both tools.

If you have the budget, go for Accurev!! It is so easy to create streams
(branches), see what have changed, and selectively merge files between
streams. Merge tracking is way ahead of Subversion! The GUI tools
provided with Accurev make it also very easy to understand the history
of a file. Accurev also gives control over what changes you want to
receive from upper streams.

If you have a small team and your needs around merging are not very
sofisticated, Subversion is a good option and free!



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-28 16:51:47 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.