On Mon, May 5, 2008 at 12:18 PM, Thiago Macieira <[EMAIL PROTECTED]> wrote: > The idea is that a private repository is for anything the developer wants. He > could be branching kdelibs for some work of his or he could be starting a new > app. Or publishing his changes to git itself. It doesn't matter. > > What matters is that we don't waste 250 MB by making him upload all objects > of > kdelibs again :-)
If the developer decides to "branch" kdelibs maineline he won't be able to make it private (read-only) cause in git (as you know I suppose :) branches of a repository are read/write for all. So the only way to make a private "branch" would be to actually clone it, that could be done on the server only by pressing a button "private clone mainline" then the user would have to download the 250MB but not upload them. At least that the only way I can see how to do read only branches, ie by actually making new clone. _______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest
