Changing a file "in-flight" makes your working copy out-of-sync with
server copy. This is not a good practice.
From: Johan Corveleyn [mailto:johan.corveleyn@...]
Sent: Thursday, 30 April 2009 9:27 AM
Cc: users@... Subject: RE: CVS to Subversion Migration
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).
Van: David Weintraub [mailto:qazwart@...]
Verzonden: woensdag 29 april 2009 22:20
CC: users@... 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
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
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@...> wrote:
> I have a question on a CVS to Subversion Migration.
> I am looking into migrating our current CVS Source repository over to
> 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
This email and any attachments are confidential. They may also be subject to copyright.
If you are not an intended recipient of this email please immediately contact us by replying
to this email and then delete this email.
You must not read, use, copy, retain, forward or disclose this email or any attachment.
We do not accept any liability arising from or in connection with unauthorised use or disclosure
of the information contained in this email or any attachment.
We make reasonable efforts to protect against computer viruses but we do not accept liability
for any liability, loss or damage caused by any computer virus contained in this email.