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

RE: CVS to Subversion Migration

From: Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be>
Date: Thu, 30 Apr 2009 01:27:12 +0200

Couldn't one use pre- or post-commit hooks to remove the cvs2svn:rev-num property whenever someone commits a change? That way, all files which were unchanged after migration keep their rev-num property, and all files which are changed afterwards have it removed. This hook would have to be enabled right after the migration though.

Haven't thought a lot about branching and merging, but I guess that should be ok as well (as soon as you commit any change, the rev-num property is removed from all changed files).


-----Oorspronkelijk bericht-----
Van: David Weintraub [mailto:qazwart_at_gmail.com]
Verzonden: woensdag 29 april 2009 22:20
Aan: Mark-E
CC: users_at_subversion.tigris.org
Onderwerp: Re: CVS to Subversion Migration

Just echoing the sentiment.

cvs2svn worked well. We did a project at a time. Just a word of
caution. Be careful with the --cvs-revnums flag. I used it and thought
it worked great. It put a cvs2svn:rev-num property on each file
version with the CVS version of that file. I figure this would come in
handy if a developer wanted to know exactly what revision a file was
in CVS.

Then, to my horror, I suddenly realized that it was putting this
property on all subsequent revisions of the file. I had to checkout
the entire source repository, remove this property, and then commit it
back again.

Merging and branching kept bringing this property back and it
generally made a mess of things for a few months. In the end, it
really didn't do anything for us. No one was really interested in the
CVS revision number anyway.

If you do use it, you must check everything out, remove the property,
and then recommit once the conversion is done.

On Wed, Apr 29, 2009 at 3:32 PM, Mark-E <meramo_at_hbs.edu> wrote:
> I have a question on a CVS to Subversion Migration.
> I am looking into migrating our current CVS Source repository over to
> Subversion.
> Most of the end users want to pull over the history as well however I am
> planning on moving code on a project by project basis.
> Basically after we modify and test a projects ant build script with
> Subversion, we will move that project to Subversion.
> I see that cvs2svn supports moving one module at a time so my question, has
> anyone out there done this and if so, what was the experience like? Did it
> work well? Are you able to move history for each project?
> Regards,
> Mark
> --
> View this message in context: http://www.nabble.com/CVS-to-Subversion-Migration-tp23300789p23300789.html
> Sent from the Subversion Users mailing list archive at Nabble.com.
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1984232
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].

David Weintraub
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-30 01:28:44 CEST

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