On Wednesday 10 March 2010 20.00.32 Andreas Pakulat wrote: > Hi, > > I'm having a problem here with the rules for the kdevelop python plugin. > The original code was in a work-branch, then a new "python" directory > was created in playground and the code moved from the work-branch into a > subdir of this new subdir (in fact branches/work/kdev-pg_python_parser > was moved to ../python/kdev-pg_pyhton_parser). And then the directory > was renamed in playground to just "parser". I've tried the following to > import the history of the plugin as well as the parser code: > > match /trunk/playground/devtools/kdevelop4-extra-plugins/python/ > repository kdevelop-python > branch master > end match > > match /branches/work/kdev-pg_python_parser/ > repository kdevelop-python > branch master > end match > > match /trunk/playground/devtools/kdevelop4-extra-plugins/python > action recurse > end match > > Unfortunately this generates a repository which has the files of the > parser subdir also in the top-level directory. So it seems like one of > the moves wasn't followed properly. > > Any suggestions how to fix this without loosing the history from the > work-branch?
If all moves are with svn history I don't think you need to do anything. The tool does it for you. /Regards Torgny _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
