From: Jonathan Nieder <jrnieder@gmail.com>
Date: Wed, 14 Jul 2010 15:39:00 GMT
Subject: Re: serving git with both "git:" and "http:" and submodules
Message-ID: <20100714153900.GB1583@burratino>
In-Reply-To: <4C3DD7EF.6010805@panasas.com>

Boaz Harrosh wrote:

> So smart people using git will just do:
> 1. $ git clone git://my-domain.org/my-tree/.git
> 2. $ git submodule init
> 3. $ git submodule update
> 
> And all is well... But smart ass corporate people would not use "git:"
> protocol because of fire-walls and for them I have a dumb "http:" export
> as:
> 1. $ git clone http://my-domain.org/trees/my-tree/.git
[...]
> So my question is: Can I automate this so people with "http:"
> clones are not forced to manually edit their config files?
> (Some users are just not up to it)

Sure.  For example, you can ship an update-submodules.sh script
to take care of checking “git config remote.origin.url” and
updating the ‘[submodule "sub"] url’ configuration to match.

Of course, even this would not make
'git clone --recursive http://my-domain.org/trees/my-tree/.git'
work.  If you can get git-http-backend working, I’d suggest using
that so you only have to deal with one url.

Hope that helps,
Jonathan