Re: denying branch creation in a shared repository

From: Sitaram Chamarty <sitaramc@gmail.com>
Date: Oct 20, 2009, 11:24 UTC
Message-ID: <2e24e5b90910200424m340c52d8rabc0b61a7bf55c45@mail.gmail.com>
In-Reply-To: <ee22b09e0910190943x51d48c09sdc50d941d643358d@mail.gmail.com>

On Mon, Oct 19, 2009 at 10:13 PM, Mohit Aron <mohit.aron@gmail.com> wrote:

Show 10 quoted lines

>>
>> That was the main reason I wrote gitolite
>> (http://github.com/sitaramc/gitolite), though now it does a heck of a
>> lot more than just that.
>>
>
> That's great. You might want to consider making it a deb package
> that's available from one of the Ubuntu/Debian repositories. An apt
> search on Ubuntu 9.10 doesn't reveal it. I usually shy away from
> installing software on my machines that is not automatically managed.

There are a couple of answers to this:

(1) I'm not really a debian guy, and definitely not ubuntu. My distro of choice for nearly 10 years has been Mandriva :-)

(2) gitolite's second reason for existence [after the one in this thread] is the need to install something on machines where you do *not* have root, can't create another user, etc etc. There was a Solaris 9 on which I couldn't install python-setuptools, and so no gitosis :-(

Regardless of all that, someone is working on it... http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550817

I respect your inclination to shy away; I do the same for pretty much everything except git itself and one or two others.

But if you don't mind looking through the documentation (browse it directly on github; it'll render the markdown properly, though the plain text is quite readable too), you may be able to better decide if you want to use it despite this limitation.

Regards,

Sita