[Kde-scm-interest] On Amarok Switching to Git

[Oswald Buddenhagen]

On Mon, Jan 19, 2009 at 08:52:23PM +0100, Thiago Macieira wrote:
> All of them contain the imported history.
> 
ok.
not that i understand the need for separate repositories for the
"live" branches in the first place, but whatever. :}

anyway, note that the historic (cvs) branches in our svn repo are still
screwed up. that means that either somebody invests time into fixing
cvs2svn and fixes the history retroactively (i have coolo's ok for that,
just no time for it) or that the history is cut (after the ad-hoc fixes
and general reorganizations that happened in svn after the import) (it
would be still possible to make the history available in git via a graft
at some later point).

btw, does any svn => git tool understand module moves within a bigger
repository or would the history before the last move be lost anyway?
that's not relevant to amarok in case it was never moved, but it
certainly affects a lot of kde in general.