On 12/13/2009 01:59 PM, Oswald Buddenhagen wrote: > the location where cvs2svn put the tags was just fine, even if somewhat > naive for actual use in svn (one could do better with current cvs2svn). > but after the git import, that will be irrelevant. i'd even try to get > back the original tag names. of course, the conversion step as such is > still something to consider.
Well, it was an issue in the case of Konvi's 0.15 tag. The tag was originally put by cvs2svn into /tags/konversation_0_15_release and later got copied to /tags/konversation/0.15. Writing a rule for the latter produced an orphaned tag in the git repo (i.e. it pointed to a commit with no parents or kid), so we had to look up that original tag and write a rule for it instead. The actual SVN revisions produced by cvs2git are also really funky: http://websvn.kde.org/?revision=367459&view=revision It copied everything and then deleted everything but the empty kdeextragear-2 superstructure and the Konvi dir. SVN era tags are of the Konversation dir direct- ly. So some recurse rules needed to be added to the ruleset to descend into the right directory. It's not rocket science, but it's knowledge/expe- rience needed to be able to use the tool success- fully, and it certainly adds some workload. > in theory cvs2svn should have already mapped that. obviously some > entries were missing or an entire case class was not considered at all. > :( Well, the CVS account name for Konvi's original project founder used to be "eisfuchs", and yet his SVN account name is "abatianni" today. All the "eisfuchs" commits happen to be from the CVS era while all the "abatianni" commits happen to be from the SVN era, so I assume that things went awry in the CVS->SVN conversion. But perhaps that is not the case and the SVN account name was chan- ged after the conversion. In any case, I had to extend the account map I used for the Konvi conversion so svn2git wouldn't import the co- mmits as "eisfuchs <eisfu...@localhost>". -- Best regards, Eike Hein _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
