You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by surendra M <su...@gmail.com> on 2006/11/06 20:27:52 UTC
Re: performance CVS Vs SVN
Agree.
But our build process heavily depends on tags. It'll checkout/update all the
specified tags
and prepares a build file. And if I adopt to SVN instead of CVS I may need
to change my
build process too. How easy it is to migrate tags from PVCS/CVS to SVN ? And
are we
able to migrate as expected? If got chance please look for the thread
"*simulating
tags like* *CVS*" posted by me.
On 10/28/06, Dmitri Colebatch <di...@colebatch.com> wrote:
>
> We're about to change from CVS to SVN and one of the major factors in the
> time taken to lay a tag. We have a large CVS repository with several years
> worth of archives. Tagging takes minutes as opposed to seconds for SVN.
>
> cheers
> dim
>
>
> On 10/29/06, Kevin Greiner <gr...@gmail.com> wrote:
> >
> > On 10/27/06, surendra M < surendrahere@gmail.com> wrote:
> > >
> > > Having an idea of migrating my repository from PVCS to CVS or SVN
> > > I did an evalution.
> > > I could see some mail posts discussing the performnace of CVS Vs SVN.
> > > But they were carried out on old version of CVS and SVN.
> > >
> >
> >
> > When my company recently switched to version control software, CVS was a
> > complete non-starter due to lack of rename support and non-atomic committs.
> > It doesn't matter how much faster CVS is, if it doesn't do what you need.
> >
>
>
--
regards
Suren
Re: performance CVS Vs SVN
Posted by Michael Haggerty <mh...@alum.mit.edu>.
surendra M wrote:
> Agree.
> But our build process heavily depends on tags. It'll checkout/update all
> the specified tags
> and prepares a build file. And if I adopt to SVN instead of CVS I may
> need to change my
> build process too. How easy it is to migrate tags from PVCS/CVS to SVN ?
> And are we
> able to migrate as expected? If got chance please look for the thread
> "*simulating tags like* *CVS*" posted by me.
The cvs2svn migration tool (http://cvs2svn.tigris.org/) converts CVS
tags to SVN 'tags' just fine.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: performance CVS Vs SVN
Posted by Bob Hiestand <bo...@gmail.com>.
On 11/6/06, Les Mikesell <le...@gmail.com> wrote:
> On Mon, 2006-11-06 at 15:27 -0500, surendra M wrote:
> > But our build process heavily depends on tags. It'll checkout/update
> > all the specified tags and prepares a build file. And if I adopt to
> > SVN instead of CVS I may need to change my build process too. How easy
> > it is to migrate tags from PVCS/CVS to SVN ? And are we able to
> > migrate
> > as expected?
>
> That's going to depend on how you set the tags. In CVS, you can
> float tags to new locations and always have known names for current
> and n-1, n-2, etc. build tags. I don't think there is any equivalent
> in SVN so the build process must be told about the tag to use and
> some external logging process used to track them.
Does "floating tags" in this context mean creating a list of files
that transparently tracks HEAD? You could do this in subversion with
symlinks and svn:externals (at least on a UNIX system).
If you're talking about updating existing tags, that's possible in
subversion as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: performance CVS Vs SVN
Posted by Les Mikesell <le...@gmail.com>.
On Mon, 2006-11-06 at 15:27 -0500, surendra M wrote:
> But our build process heavily depends on tags. It'll checkout/update
> all the specified tags and prepares a build file. And if I adopt to
> SVN instead of CVS I may need to change my build process too. How easy
> it is to migrate tags from PVCS/CVS to SVN ? And are we able to
> migrate
> as expected?
That's going to depend on how you set the tags. In CVS, you can
float tags to new locations and always have known names for current
and n-1, n-2, etc. build tags. I don't think there is any equivalent
in SVN so the build process must be told about the tag to use and
some external logging process used to track them.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org