Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
I think that, depending on how the git import script works, some issues might actually disappear "magically". But there are others that won't. For example the fact that split points are not associated with a CVS commit, so you have to fake one (something that the current git import apparently doesn't).
I have specifically and manually removed the fake split commits after importing from SVN, because they didn't add information AFAICS. Why would you want them in the repository?
Importing from the svn export should work, I expect it's mainly a question of defining how repository paths should be mapped to git branches. (Are git branch names version controlled? In the svn export the main development branch is renamed 0.5->0.6->0.7->7.0->7.1->7.3->7.5->7.7 at apropriate times.)
Git branches can be demoted to tags at the flip of a switch at anytime, and that probably is what we should be doing. I.e. in git, after the 7.8/7.9 split, I'll be changing the 7.7 branch to become a tag, and then copy that tag into 2 branches, 7.8 and 7.9. Whereas "master" is then pointing to 7.9, but that is just convention in git, and doesn't have a lot of realworld implications.