Changes to our Git infrastructure

Martin Klapetek martin.klapetek at
Sun Dec 28 23:38:08 GMT 2014

On Sun, Dec 28, 2014 at 11:23 PM, Ben Cooksley <bcooksley at> wrote:

> Hi all,
> Based on the current feedback:
> 1) It seems people see no use in clone repositories.
> 2) Little commentary has been made on the merits of scratch
> repositories, with some dismissing them as pointless.

> Therefore sysadmin proposes that both clone and scratch repositories
> be eliminated as a concept with the next iteration of our Git
> infrastructure.

Noooo not scratch repos. I can see clones being useless as branches
in the actual repos should be used instead, but I personally consider
scratch repos a very useful thing, for example to host simple projects
that shouldn't be part of any main/big module - they are much more
easier to set up than proper repositories - mostly because they don't
require manual sysadmin actions (and fileing tickets by the developer),
it's a personal git space readily available.

The negative side is the repo propagation - it does take a while
for the repo to appear for example in quickgit -> so links cannot be
posted for viewing online immediately. Imo if this is solved, scratch
repos would be quite useful.

Also just looking at quickgit.k.o, there is about 1000 scratch repos
currently, so it looks it's in a good use (though granted, many of the
repos may be outdated and are just overdue for removal).

Martin Klapetek | KDE Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the kde-core-devel mailing list