Help converting a large repository
Giulio Eulisse <[email protected]> Sat, 13 Apr 2013 00:02:49 +0200
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
Dear all,
I've a rather large repository which I would like to convert to git. The current repository layout in CVS is a two layer structure
SubSystem/Package
where each package is tagged independently with a VXX-YY-ZZ tag. The release is than assembled from a list of pairs
[(SubSystem/Package, Tag)]
which is stored in separate database (yuk... I know). The release is then tagged with a global tag and I do know both the order in which the global tags where done, e.g.
v5_3_0 -> v5_3_1 -> v6_0_0
and the possible branch points, e.g.:
> v5_3_2 -> v5_3_3
/
v5_3_0 -> v5_3_1 -> v6_0_0
given I do no care about the per package tags, but only the global tags, I would have expected that simply having a symbols-hints file which does:
. v5_3_0 tag . .
. v5_3_1 tag v5_3_0 .
. v5_3_2 tag v5_3_1 .
. v5_3_3 tag v5_3_2 .
. v6_0_0 tag v5_3_2 .
would have solved my problem, but it does not. In particular I'm not sure how to make sure v5_3_1 actually results in a new branch (let's call it v5_3_X branch), and I'm not sure how to deal with the per package branches which pollute the repository, but which I do not care about. Any hint of what I should look for?
--
Ciao,
Giulio
------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=3053190
To unsubscribe from this discussion, e-mail: [[email protected]].