Re: Non-unique tag names across projects that should not be merged during conversion to svn
Michael Haggerty <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
On 06/24/2011 09:46 PM, Vasanth Velusamy wrote:
> [...] during migration to svn using cvs2svn, I would like to have
> one tag in svn for each tag in each project. [...]
>
> Let me give an example of the situation. I have two projects projA and
> projB in CVS. There would be tags named Build-1, Build-2, etc. in projA,
> also tags Build-1, Build-2, etc. in projB. When I run cvs2svn with
> -symbol-default at 'heuristic', the migration tool assumes that the tags
> used in projA and projB which have the same name are the same, and
> merges them and creates one tag each for Build-1, Build-2, etc. in svn.
>
> What I need is something like ProjA-Build-1, ProjB-Build-1,
> ProjA-Build-2, ProjB-Build-2, etc. in svn. 'heuristic' doesn't do
> that. Seems like the other symbol-default options (strict, branch, tag)
> are not going to be helpful here either.
Usually if you want separate tags for different parts of your
repository, you should convert each part as a separate project (in the
cvs2svn sense) by doing a multiproject conversion [1]. This will create
{trunk, branches, tags} directories for each project and treat CVS
symbols within each project as unrelated to each other. (In your
example, you will get symbols at $SVNURL/ProjA/tags/Build-1,
$SVNURL/ProjB/tags/Build-1, $SVNURL/ProjA/tags/Build-2,
$SVNURL/ProjB/tags/Build-2, etc.)
Michael
[1] http://cvs2svn.tigris.org/faq.html#onetoone
--
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/
------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2775562
To unsubscribe from this discussion, e-mail: [[email protected]].