[Kde-scm-interest] Tracking moves without losing history

Niko Sams niko.sams at gmail.com
Sun Dec 12 15:49:26 CET 2010


Hi,

I have problems with losing all history when a repository got moved.
(1) First (correctly working) example is the move of marble from
playground to kdereview:
    662514 (.. and moving the docs into the right place ...)
playground -> kdereview: 662511 (Moving Marble into kdereview - yay!)
    662505 (add a CMakeList.txt)
this is detected correctly, rev 662514 and 662505 show up as commits,
662511 not.

(2) However the move from kdereview to kdeedu breaks the history:
    669526 (ChangeLog)
kderveview -> kdeedu: 669496 (Moving Marble into KDE-Edu after
receiving green light from annma)
    669486 (Some fixes:)
History starts with 669496, all former commits are lost.


What I have found out is that the difference between those is that in
(1) svn_fs_paths_changed reports
first the delete first and the add second, while for (2) it is the
other way around.
But how to solve the problem?
Please, someone with more knowledge about svn2git, take a look at it :D

thanks,
Niko



To reproduce use this rule file:
create repository KDE/kdeedu/marble
end repository

match /trunk/playground/base/(marble)/
  repository KDE/kdeedu/\1
  branch master
end match

match /trunk/kdereview/(marble)/
  repository KDE/kdeedu/\1
  branch master
end match

match /trunk/KDE/kdeedu/(marble)/
  repository KDE/kdeedu/\1
  branch master
end match

match /
end match

and those commands:
svn-all-fast-export --add-metadata --identity-map
../kde-ruleset/account-map --rules ../kde-ruleset/marble-test
--resume-from 669486 --max-rev 669526 --debug-rules ../svn
svn-all-fast-export --add-metadata --identity-map
../kde-ruleset/account-map --rules ../kde-ruleset/marble-test
--resume-from 662504 --max-rev 662514 --debug-rules ../svn


More information about the Kde-scm-interest mailing list