Re: CVS to Subversion Migration

The only way to remove this property would be to do a massive
checkout, remove the property, and then do a second commit.
Auto-properties are for adding properties to new files. It's to get
around a problem of having your commit be rejected because a
particular file needs a particular property attached to it. These
files are already existing, and you're trying to remove a property,
not add one.

You can do it programmatically which is what I did. The whole script
took me a few minutes to write. However, the checkout and commit took
a loooong time.

In the end, we didn't find the cvn2svn:revnum too useful. No one ever
needed that information, and when you think about it, the developers
never referred to the CVS revision number anyway. They always used the
log entry, the branch, or the tag which Subversion brings over anyway.
If I had to do the conversion over, I'd simply leave it out.

My whole point was a warning to others not to be seduced by this cvs2svn option.

On Thu, Apr 30, 2009 at 3:35 AM, Johan Corveleyn
<johan.corveleyn_at_uz.kuleuven.ac.be> wrote:
> Hm, right, I forgot about that.
>
> Could you do it by using auto-props on the client side then (needs to be deployed on all clients though)? Can you remove properties with auto-props?
>
> Johan
>
> -----Oorspronkelijk bericht-----
> Van: Srilakshmanan, Lakshman [mailto:lakshman.srilakshmanan_at_police.vic.gov.au]
> Verzonden: donderdag 30 april 2009 1:57
> Aan: users_at_subversion.tigris.org
> Onderwerp: RE: CVS to Subversion Migration
>
> Hi John,
>
> Changing a file "in-flight" makes your working copy out-of-sync with
> server copy. This is not a good practice.
>
> Thanks
> Lakshman
> -----Original Message-----
> From: Johan Corveleyn [mailto:johan.corveleyn_at_uz.kuleuven.ac.be]
> Sent: Thursday, 30 April 2009 9:27 AM
> To: Mark-E
> Cc: users_at_subversion.tigris.org
> 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).
>
> Regards,
> Johan
>
> -----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&dsMessag
>> eId=1984232
>>
>> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe_at_subversion.tigris.org].
>>
>
>
>
> --
> David Weintraub
> qazwart_at_gmail.com
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageI
> d=1984912
>
> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe_at_subversion.tigris.org].
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageI
> d=1987111
>
> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe_at_subversion.tigris.org].
>
> ================================================================================================
> EMAIL DISCLAIMER
>
> 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.
> ================================================================================================
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1987772
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1992616
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
>

-- 
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1998487
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].