Re: cvs2svn migration: making cvs branch as svn trunk while migration
Michael Haggerty <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
ravi wrote: > Right now we release based on branch and our cvs head needs lot of clean > up to make it look like production. so we wanted to migrate to svn and > make the current release branch as trunk on svn and do not need to > migrate any other tags, branches. There is no way to exclude trunk. Every branch sprouts from trunk. Therefore if trunk were excluded, part of the branch history would not be available. (I suppose that this could be changed by pretending that the "trunk" part of the branch history were actually on the branch, but this is not implemented in cvs2svn and would be a bit of work.) What you can do is to have the branch written to an SVN path called "trunk" and trunk written to some other SVN path. All other branches and tags could be excluded (as long as the branch you want always sprouts from trunk). This is most easily done via a symbol-hints file. See the --write-symbol-info and --symbol-hints options for more information. Michael ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2616229 To unsubscribe from this discussion, e-mail: [[email protected]].