Sysadmin Load Reduction: Subversion Infrastructure

Jack ostroffjh at
Tue Nov 12 14:48:35 GMT 2019

On 11/12/19 7:11 AM, Luigi Toscano wrote:
> Māris Nartišs ha scritto:
>> pirmd., 2019. g. 11. nov., plkst. 16:02 — lietotājs Luigi Toscano
>> (<luigi.toscano at>) rakstīja:
>>> Alexander Potashev ha scritto:
>>>> вс, 10 нояб. 2019 г. в 18:09, Luigi Toscano <luigi.toscano at>:
>>>>> Nate Graham ha scritto:
>>>>>> On 11/9/19 4:50 PM, Nicolás Alvarez wrote:
>>>>>>> El sáb., 9 de nov. de 2019 a la(s) 20:29, Nate Graham (nate at escribió:
>>>>>>> - Experiment conversion to git and see if the resulting repo(s) are of
>>>>>>> a reasonable size (I vaguely recall seeing bad results with this)
>>>> I expect that a single Git repository would be several GBs in size.
>>> For the record, the current checkout (without svn metadata) of trunk/l10n-kde4
>>> (ok, no more needed), branches/stable/l10n-kde4, branches/stable/l10n-kf5,
>>> branches/stable/l10n-kf5-plasma-lts, trunk/l10n-kf5 and trunk/l10n-summit is
>>> ~11 GiB. The trunk/l10n-kf5 branch alone is 5.3 GiB.
>> One of pro sides of SVN still is ability to work with a single
>> directory instead of whole repo. For Latvian language it means using
>> only ~300MB of disk space (I have less than 1GB free space on my
>> laptop). Thus if a move to GIT is planned, I would vote to have a
>> separate repo for each language.
> Right, but that would make the life of people doing bulk changes (like me)
> much more complicated. Right now I can do all the changes in one shot. That's
> part of the problem.

Would git submodules help with this?  I can imagine it would be an 
effort to get it set up, but then you have everything in one place.


More information about the kde-community mailing list