On Tue, Dec 1, 2015 at 6:50 PM, laurent Montel <mon...@kde.org> wrote:
> Le lundi 30 novembre 2015, 22:43:36 CET Ben Cooksley a écrit :
>> Hi Pim devels,
>
> Hi,
> So I reorganized source yesterday.
> I verified that all was ok
> So how I do now to split ?

The splitting of the repositories can be conducted using several means:

1) Filter branch, where the history is kept in each individual repository
2) Grafts, where the history is kept in the original repository, and
is attached by the developer when it is needed. This is how both Qt
and Frameworks did their 4 -> 5 splits I believe.

As for how either method is done, i'm afraid that is something i'm
unfamiliar with - someone on the list should know however.
Please ensure you have performed initial test splits, including
generation of the repositories before proceeding with any pushing of
repositories.

Cheers,
Ben

>
> Regards
>
>> I've received a slew of tickets which appears to be laying the ground
>> work for splitting out all the PIM libraries into separate
>> repositories.
>>
>> Before this happens can we:
>>
>> 1) Confirm this is the appropriate way to split it
>> 2) Confirm the code is ready to build independently, and that no cross
>> dependencies exist
>> 3) Look into reviewing how the repositories will be populated - will
>> they be the same as the kdelibs -> frameworks split?
>>
>> Just a bit concerned as I haven't seen anything about this anywhere
>> until I got a pile of tickets in my inbox.
>>
>> Thanks,
>> Ben
>> _______________________________________________
>> Kde-frameworks-devel mailing list
>> Kde-frameworks-devel@kde.org
>> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>
>
> --
> Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software Engineer
> KDAB (France) S.A.S., a KDAB Group company
> Tel. France +33 (0)4 90 84 08 53,  http://www.kdab.fr
>
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Reply via email to