Or you should setup your own gitweb, git clone Koha using git protocol as normal, then clone on client's system via HTTP to your repo.
HTTP is exceedingly less efficient than the git protocol, so it is not that strange to see it disabled. --Joe On Thu, Sep 3, 2009 at 1:08 AM, savitra sirohi <savitra.sir...@osslabs.biz>wrote: > Hi Chris, two of our customers have the git port blocked on their > firewalls. And it is hard for them to get firewall configurations > changed quickly. > > I am sure it will help a lot of people if cloning were possible on port 80. > > Thanks, > Savitra Sirohi, > Nucsoft OSS Labs > http://www.osslabs.biz > > On 9/3/09, Chris Cormack <ch...@bigballofwax.co.nz> wrote: > > 2009/9/3 savitra sirohi <savitra.sir...@osslabs.biz>: > >> Hello, wanted to report this problem: > >> > >> I am unable to clone the maintenance branch over http: > >> > >> linux-yx85:~ # git clone > >> http://git.koha.org/pub/scm/koha-maintenance.git > >> koha-maintenance-clone > >> Initialize koha-maintenance-clone/.git > >> Initialized empty Git repository in /root/koha-maintenance-clone/.git/ > >> warning: remote HEAD refers to nonexistent ref, unable to checkout. > >> > > I'm not sure that it is set up for cloning over http > > > > I have always cloned over git:// > > > > Does your firewall block you from cloning over git:// ? > > > > Chris >
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
