Am 15.12.2011 02:25, schrieb Martin Zibricky:
> Hartmut Goebel píše v Út 13. 12. 2011 v 16:50 +0100:
>> should we recreate merges when migrating to git? This would yield a
>> more 
>> complete history, but may be *much* work. 
> What does it practically mean? Something like recreate changesets?

Basically just adding "parent" nodes. If a node is a merge, it gets
additional parent nodes.

This should be easy and useful for "branch ends", e.g. when the a
feature branch is merged into trunk.

Another idea is to use the infos from svn-merge create more `parent`
relations. But doubt this is worth the effort.

> btw, I found another tool for migrating between VCS systems:
>
> http://progetti.metapensiero.it/tailo

This seams to support `hooks`, which may ease some of the tasks we need
to do.

I did some test with reposurgeon yesterday, but did not manage to remove
even a simple wrong tagging (svn cp tunk tags/wrong-release).

I propose to convert to git using git-svn and then do all the cleanup on
the git repository. This is based on my own tests and other readings
(http://blog.futurice.com/migrating-svn-repos-with-full-history-to-git,
http://blog.smartbear.com/post/10-12-16/migrating-from-subversion-to-git-lessons-learned/)
.

-- 
Schönen Gruß - Regards
Hartmut Goebel
Dipl.-Informatiker (univ.), CISSP, CSSLP

Goebel Consult 
Spezialist für IT-Sicherheit in komplexen Umgebungen
http://www.goebel-consult.de

Monatliche Kolumne: http://www.cissp-gefluester.de/
Goebel Consult ist Mitglied bei http://www.7-it.de


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to