Re: cvs2git "merge based on commit messages"
Michael Haggerty <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
On 11/10/2010 03:32 PM, [email protected] wrote: >>> One feature I miss in cvs2git comparing to "git cvsimport" is >>> the approximative creation of merge-links between branches based >>> on commit messages (like "merged from RELEASE_1_2"). >> >> I'm not familiar with that feature, but it sounds like fun. How >> does it work in "git cvsimport"? > > It is fun, as it is a very rough heuristic, but seemed to work quite > good. Although I would not rely on it, at least it gave some relevant > linking information about the branches. Thanks for the info. > By the way, you could mention in git-move-refs.py that it supersedes > git-move-tags.py and git-move-refs.py, because it took me some time > to find this out. git-move-tags.py could be removed from contrib/ > right? git-move-tags.py has already been removed from trunk, and I believe has been removed from the current documentation. If you find any overlooked references, please let me know. You are probably using release 2.3. Given that you are converting to git, I suggest you try the trunk version of cvs2git. I believe it to work better. Michael -- Michael Haggerty [email protected] http://softwareswirl.blogspot.com/ ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2680902 To unsubscribe from this discussion, e-mail: [[email protected]].