Re: Repository as Branch

Vicky Chester wrote:
> When we created the customer's CVS repositories, we just took a copy of
> the working copy from the core repository and checked it into a new
> repository, rather than copying the repository itself. It sounds like
> this wouldn't provide enough information to link the history together;
> there would just be the date the customer file was checked in, which
> might not be the date it was branched. 

If you always checked the snapshot into the new repository *before*
making changes, then it might be possible to find the branching point
based on the contents of the files being identical.  Otherwise it would
be very tricky.

> Setting up the fake branches sounds like the most straightforward
> solution. Would this give a problem merging the branch changes back into
> the core later on? 

Merging will not work because (1) SVN doesn't know that the branch is
related to the trunk and (2) SVN doesn't know which trunk revisions are
already on the branch.

You could create fake merge info based on some external knowledge about
when the branches diverged.  But I'm not sure; it might be that SVN will
refuse to merge anyway because of (1).

By the way, you didn't mention whether the individual CVS repositories
*themselves* have branches and tags.  This could change how you want to
configure the conversion.

Michael

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2592382

To unsubscribe from this discussion, e-mail: [[email protected]].