[Kde-pim] Git migration status

[Torgny Nyblom]

On Sunday 18 April 2010 14.07.10 Ingo Klöcker wrote:
[...]
> You forgot the obvious:
> - Splitting the repo into multiple per-application repos.

I was under the impression that this has been decided on the KDE level and 
that the decision was no. 

> As for "Cutting off the history at some defined date", I'm against this.
> git-clone supports shallow cloning. So, there's no reason to cripple the
> master repository just because for some people cloning the full
> repository is problematic. Those people will have to live with a few
> limitations:
>   A shallow repository has a number of limitations (you cannot clone or
>   fetch from it, nor push from nor into it), but is adequate if you are
>   only interested in the recent history of a large project with a long
>   history, and would want to send in fixes as patches.
> 
> Not being able to push is of course a serious limitation, but I think
> this limitation could be circumvented more or less easily by providing
> an email service which automatically pushes patches that are sent to
> this address. Of course, there needs to be some kind of authentication
> scheme (e.g. the patches resp. the messages could be OpenPGP/MIME
> signed).

Sound ok to me. The big download is a onetime deal anyway, but I do think that 
the email service sounds dangerous.

/Regards
Torgny
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/