From: Boaz Harrosh <bharrosh@panasas.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: serving git with both "git:" and "http:" and submodules
Date: Wed, 14 Jul 2010 18:58:50 +0300 [thread overview]
Message-ID: <4C3DDEBA.8010509@panasas.com> (raw)
In-Reply-To: <20100714153900.GB1583@burratino>
On 07/14/2010 06:39 PM, Jonathan Nieder wrote:
> 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'
Right
> work. If you can get git-http-backend working, I’d suggest using
> that so you only have to deal with one url.
>
Ok I'll dive into "git-http-backend" (any pointers). But I thought
this one will still serve me an "http:" url. Are you suggesting to
just drop the "git:" protocol? (Since "git-http-backend" is just as
good, through http?)
> Hope that helps,
> Jonathan
But a script for users might be a very good idea. I might even add
it to the main Makefile. And make it totally transparent.
$ git-clone; make;
Thanks that actually helped
Boaz
next prev parent reply other threads:[~2010-07-14 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 15:29 serving git with both "git:" and "http:" and submodules Boaz Harrosh
2010-07-14 15:39 ` Jonathan Nieder
2010-07-14 15:58 ` Boaz Harrosh [this message]
2010-07-14 16:12 ` Jonathan Nieder
2010-07-15 14:07 ` Brad King
2010-07-15 6:46 ` Peter Krefting
2010-07-15 7:41 ` [PATCH] gitmodules.5: url can be a relative path Jonathan Nieder
2010-07-15 7:51 ` [PATCH] Documentation: add submodule.* to the big configuration variable list Jonathan Nieder
2010-07-15 9:34 ` Johan Herland
2010-07-15 23:12 ` Jonathan Nieder
2010-07-15 9:32 ` [PATCH] gitmodules.5: url can be a relative path Johan Herland
2010-07-15 10:13 ` Boaz Harrosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C3DDEBA.8010509@panasas.com \
--to=bharrosh@panasas.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.