[Kde-scm-interest] kdelibs official branches import finished

Johannes Sixt j.sixt at viscovery.net
Fri Dec 28 13:32:43 CET 2007


Thiago Macieira schrieb:
> Johannes Sixt wrote:
>> Thank you, Thiago, for you efforts! This *is* exciting.
>>
>> Thiago Macieira schrieb:
>>> after repack:
>>> $ du -sh
>>> 239M    .
>>>
>>> Other stats:
>>> $ git count-objects -v
>>> count: 0
>>> size: 0
>>> in-pack: 547980
>>> packs: 1
>>> prune-packable: 0
>>> garbage: 0
>> These numbers tell that even for single modules, a whole-history
>> conversion to git is not feasible for daily work, IMHO. Of course, it's
>> nice to have a historic repo around somewhere, but for future work it is
>> better not to be burdened with prehistoric revisions when they take so
>> much space.
> 
> Huh!?
> 
> This is the Qt repository where daily work does happen:
> $ du -sh .git/objects
> 831M    .git/objects
> 
> $ git count-objects -v
> count: 5094
> size: 22432
> in-pack: 1163310
> packs: 2
> prune-packable: 0
> garbage: 0
> 
> [There's one .keep file for a large .pack]

Local disk usage does not worry me. It's the network traffic of a clone
that we should keep low. Keep in mind that you are exchanging this repo
basically in a LAN.

We should not expect that every casual KDE contributor has to download
250M for kdelibs, 250M for kdebase, and several dozens of megs for each
other module - just to fix a buglet.

But, oh well, there is the shallow clone feature, which could reduce the
traffic to a minimum. Except that shallow clones are crippled: You can't
fetch from nor push into them. So, if you want a full-featured clone, you
have to have a full clone. In which case many people really will have a
second thought before they download 500+M. It scares away people.

-- Hannes



More information about the Kde-scm-interest mailing list