[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-scm-interest
Subject:    Re: [Kde-scm-interest] KDE Git hosting status update
From:       Jeff Mitchell <mitchell () kde ! org>
Date:       2010-06-11 14:41:53
Message-ID: 4C124B31.1050206 () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On 6/11/2010 9:00 AM, Johan Sørensen wrote:
> 2010/6/11 Jeff Mitchell <mitchell@kde.org>:
> [snip]
>>> --------------------------------------------------------------------------------
>>> SUM:                           2740          43131          44892
>>>   250546
>>> --------------------------------------------------------------------------------
>>>
>>>
>>> So, sorry for publishing bullshit numbers.
>>
>> Well, according to cloc it's not bullshit. There's clearly a large
>> disconnect here between what cloc says and what the Gitorious guys are
>> saying -- by nearly two orders of magnitude. I'd be interested in
>> knowing if the Shortcut guys have an explanation for the huge difference.
> 
> Everything in vendor/ can basically be excluded (at least in my
> opinion) as that is third-party libraries and frameworks such as
> Rails. If you decide that should be included, then cloc is probably
> correct...

Ah, that makes sense. I had forgotten that there was so much included in
vendor/.



>>
>>>> Secondly, gitorious.org does in fact use the native git-daemon, but
>>>> the document seems to confuse cloning and pushing on a few occasions.
>>>> Pushing is entirely done through SSH and once the initial auth with
>>>> gitorious is done, it's passed along to the git machinery.
>>>
>>> The point was though that the script that gets called as login
>>> shell on SSH connect relies on the Rails process to be running,
>>> which is a pretty big affair, while gitolite doesn't have any
>>> continually running daemon process involved in push access.
>>
>> I've read through the document a few times and don't see where there's
>> any confusion as to git daemons. Gitorious does indeed have a custom git
>> daemon (which you refer to as a proxy, which is a fair assessment),
>> necessary to resolve the friendly URL names into the on-disk layout.
>> This does mean that if the native upstream Git git-daemon acquires new
>> features or capabilities that we'd have to code it into your git-daemon
>> or wait for an update.
> 
> I was referring to this section: " The software uses a custom
> git-daemon, which it uses to control push access. This means that
> future features of Git (such as improved compression) are unavailable
> to KDE in the long term unless Shortcut updates their git-daemon or we
> update it ourselves."

I believe this is a simple typo. s/push/pull/ is probably what was meant
by whoever wrote that bit. In that context the above statement reads
correctly.

> Anyway, in the end it doesn't matter for you guys anymore as you've
> made a different choice already. I just wanted to point out a few
> smaller errors that I saw as a developer of Gitorious (as you know,
> these things have a tendency to be suddenly taken as facts down the
> line).

Sure, makes sense.

--Jeff


["signature.asc" (application/pgp-signature)]

_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest


[prev in list] [next in list] [prev in thread] [next in thread]