[Kde-scm-interest] git-svn import of SVN?

[Johannes Sixt]

Thiago Macieira schrieb:
> The information I was proposing to throw away are the sequential relationships 
> between commits in different modules. 
> 
> That is:
>  - revision N in Subversion is a commit to kdelibs
>     becomes kdelibs.git shaX
>  - revision N+1 is a commit in kdebase
>     becomes kdebase.git shaY
> 
> The only way to properly order shaX and shaY is through the supermodule 
> KDE.git containing two commits (shaZ1 and shaZ2) that indicate the state of 
> the submodules. I.e., in shaZ1, the kdelibs submodule changes to head shaX 
> and in shaZ2, kdebase submodule changes head shaY leaving kdelibs unchanged.

Now, *that* is certainly not needed, and is also not what _I_ was thinking 
about.

I would have generated a commit in KDE.git only for cross-module SVN commits 
as well as when a module was added/deleted/renamed. And, of course, also for 
tagged releases. Probably also for other important events, for some 
to-be-defined consensus of "important".

BTW, I'm not sure whether you are aware that KDE.git must have the branches, 
too. Your description of KDE.git above suggests that you mean that there is 
only a single, linear string of commits in KDE.git. This cannot be so.

-- Hannes