From: Brad King <brad.king@kitware.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: serving git with both "git:" and "http:" and submodules
Date: Thu, 15 Jul 2010 10:07:19 -0400 [thread overview]
Message-ID: <4C3F1617.7020706@kitware.com> (raw)
In-Reply-To: <20100714153900.GB1583@burratino>
On 07/14/2010 11:39 AM, Jonathan Nieder wrote:
> Boaz Harrosh wrote:
>> So my question is: Can I automate this so people with "http:"
>> clones are not forced to manually edit their config files?
Almost.
> Of course, even this would not make
> 'git clone --recursive http://my-domain.org/trees/my-tree/.git'
> work.
Firewall-ed users can just run
$ git config --global url.http://my-domain.org/.insteadOf git://my-domain.org/
*once* per user per machine, or even
$ git config --global url.http.insteadOf git
if they want to be really aggressive. After that they can just
pretend to use the git protocol and all URLs will be mapped under
the hood:
git clone --recursive git://my-domain.org/...
-Brad
next prev parent reply other threads:[~2010-07-15 14:16 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
2010-07-14 16:12 ` Jonathan Nieder
2010-07-15 14:07 ` Brad King [this message]
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=4C3F1617.7020706@kitware.com \
--to=brad.king@kitware.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).