[Kde-scm-interest] Gitolite server-side clones and personal branches
mitchell at kde.org
Sat Jun 12 17:19:10 CEST 2010
This question came up on a private list, but since it's relevant to many
here I figure I'll post here too.
>> * is there a way to do a server-side clone?
>> The point that if I want to have online a personal clone of KOffice I
>> to upload a 350Mb repo.
There was an admin-defined-command called fork that I had forgotten
about that does just this. Last night, after posing some questions to
Sitaram about it in an IRC message, I woke up this morning to find that
not only does this capability already exist, but that due to my
questions he now has it implemented using the -l flag to git clone so
that it uses hard links when possible, which should help keep space use
down. (This guy rocks!)
Owners of a repository (the creator) can also send a "rmrepo" command to
delete their own clones.
This is also separate from the "personal branches" feature that lets you
have branches for personal work in the main repository but in a specific
namespace (including username).
There are pros and cons to each; in general I prefer the personal
branches approach, although it can mean some more data transfer due to
extra refs/objects, because it a) is far more discoverable and b) these
branches would show up in cgit/redmine, as opposed to personal clones
that would have to either be set up as a subproject in redmine or added
to the cgit configuration (though for the cgit side of things, this
configuration could be created in a scripted fashion). However, these
would have to be used wisely and deleted when possible to avoid an
ever-increasing and unwieldy repository.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20100612/32990dab/attachment.sig
More information about the Kde-scm-interest