From: Boaz Harrosh <bharrosh@panasas.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: serving git with both "git:" and "http:" and submodules
Date: Wed, 14 Jul 2010 18:29:51 +0300 [thread overview]
Message-ID: <4C3DD7EF.6010805@panasas.com> (raw)
I have a public tree that I maintain for users. The tree is consisted
of a main-tree and a submodule tree which is also served from the same
server.
The main tree:
git://my-domain.org/my-tree/.git
The sub-tree:
git://my-domain.org/my-tree/sub/.git
in my .gitmodule I have the usual
[submodule "sub"]
url = git://my-domain.org/my-tree/sub/.git
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
With them, step 3 above will not work. My current instructions
for them is that after the step 2 "git submodule init" they should
manually edit my-tree/.git/config and change to:
[submodule "sub"]
- url = git://my-domain.org/my-tree/sub/.git
+ url = http://my-domain.org/trees/my-tree/sub/.git
And then do step 3 to clone the sub-module.
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)
Thanks, (Sorry if that has been raised before. Couldn't find any.)
Boaz
next reply other threads:[~2010-07-14 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 15:29 Boaz Harrosh [this message]
2010-07-14 15:39 ` serving git with both "git:" and "http:" and submodules Jonathan Nieder
2010-07-14 15:58 ` Boaz Harrosh
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=4C3DD7EF.6010805@panasas.com \
--to=bharrosh@panasas.com \
--cc=git@vger.kernel.org \
/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).