Re: why unlabeled Branches will come from cvs2svn
Michael Haggerty <[email protected]> Wed, 07 Jul 2010 15:30:11 +0200
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.devel |
|---|---|
| Message-ID | <[email protected]> |
Sunny wrote: > What is the reason to get the unlabeled Branches from the converstion of > cvs to > svn through the using of cvs2svn tool. > > What are the scenarios to get like those branches from CVS in SVN > conversion and > how can we avoid those branches. > > Please help anyone, my work is totally stopped at this unlabeled branches. Unlabeled branches are branches that have revisions in CVS but for which no symbol name is stored. This can happen if somebody manually deletes a branch name, for example using a command like "cvs tag -B -d BRANCH". cvs2svn doesn't want to lose any data, so it creates names like "unlabeled-1.2.3" for such branches. They're pretty useless, though, because each file typically has a different branch name for what used to be a single branch. You can exclude unlabeled branches (assuming that no *other* branch sprouts from them) using an option like "--exclude=unlabeled.\*". Please note that the argument to "--exclude" is a regular expression, not a glob pattern, and therefore an arbitrary sequence of characters is expressed as '.*' not '*'.) Michael ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2630512 To unsubscribe from this discussion, e-mail: [[email protected]].