[Kde-scm-interest] kdenetwork Git migration

[Jeremy Whiting]

Hmm, actually looking deeper kcm_krfb in svn is an empty folder (not sure
what it's for...)

And the differences in kppp seem weird, http://paste.kde.org/759278/ but
shouldn't affect anything from what I can see. so maybe we're good to go?
should I push this into the main git repos and we can test there? Rerun the
conversion if needed, etc.

BR,
Jeremy


On Wed, Jun 5, 2013 at 10:52 AM, Jeremy Whiting <jpwhiting at kde.org> wrote:

> Urs,
>
> I just ran a conversion, and cloned the result and found two problems.
>  One is krfb git repo doesn't have kcm_krfb folder inside it.  Looking at
> the CMakeLists.txt it's not built anyway, but we need to find out why it's
> not there at all imo.
>
> The second problem is that kppp has many differences between svn master
> and git master, not sure why, but I'll look into it this evening.  We need
> these to be working and right before we remove from svn.
>
> thanks,
> Jeremy
>
>
> On Wed, Jun 5, 2013 at 5:03 AM, Raphael Kubo da Costa <rakuco at freebsd.org>wrote:
>
>> Urs Wolfer <uwolfer at kde.org> writes:
>>
>> > kdenetwork will get migrated to Git in the next days (between June 5th
>> > and June 11th). Please do not commit anything into SVN anymore. Also,
>> > please wait with any Git commits until further notice.
>>
>> Sorry if I've missed this being discussed somewhere else, but doesn't it
>> make sense to ask the sysadmins to svn lock kdenetwork to prevent people
>> from committing?
>> _______________________________________________
>> Kde-scm-interest mailing list
>> Kde-scm-interest at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-scm-interest
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20130605/91ad4417/attachment.html>