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

[Thiago Macieira]

Em Wednesday 07 November 2007 14:46:25 Johannes Sixt escreveu:
> So it boils down to the question is: Is a history of the supermodule
> KDE.git worthwhile to have, or is it sufficient to start a brand new
> KDE.git only after its modules are ready?

I actually didn't answer the question.

I think a KDE.git is useful because it can allow us to split the submodules 
using git. Since the number of official branches is limited, it's not 
difficult to split up by hand later.

But that import is not the KDE.git supermodule we will have later. I don't 
think it'll be a big loss if the KDE.git supermodule contains no history 
(and, therefore, doesn't allow a checkout of the exact revisions back in 
history). 

The import will probably preserve the SVN revision numbers, so if you *really* 
need to get the same kdelibs and kdebase state at a point in time, you go by 
that.

It wouldn't be impossible, though, to modify the fast-export tool to write the 
supermodule as well.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20071107/5a5a74e4/attachment.pgp