Re: Advice on dealing with "unlabeled" branches
Michael Haggerty <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
On 10/29/2011 09:08 PM, Ryan Boggs wrote: > I'm trying to convert an old cvs repo to git using cvs2git, which > seems to be working well for the most part. My issue stems from all > the "unlabeled" branches that result from the conversion process, I am > not 100% sure the best course of action to deal with these. I've been > searching google for the past couple of days but came up with very > little on this scenario or suggested approaches. Does anyone have any > links or ideas as to how some of these situations have been handled? > Some of these generated branches contain tags that I would like to > keep (or transfer to the master branch if possible). Any advice on > this situation is greatly appreciated. This has been discussed on the mailing list many times. I thought we had a FAQ entry about it, but surprisingly we do not. (We should!) Unlabeled branches result from CVS branches that somebody tried to delete using "cvs tag -d", which deletes the *name* of the branch but not the revisions associated with it. Usually an unlabeled branch is worthless; otherwise why would somebody have tried to delete it? But if in some particular case an unlabeled branch is interesting, you are pretty much on your own because such a branch does not contain enough information to recreate it with any amount of confidence. You can use some cvs2svn tools to help (e.g., see issue 128 [1]) but it will essentially be a manual process. Michael [1] http://cvs2svn.tigris.org/issues/show_bug.cgi?id=128 -- Michael Haggerty [email protected] http://softwareswirl.blogspot.com/ ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2869078 To unsubscribe from this discussion, e-mail: [[email protected]].