From: Andreas Krey <a.krey@gmx.de>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Tim Visher <tim.visher@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Git Submodule Usage Pattern
Date: Tue, 16 Feb 2010 21:00:35 +0100 [thread overview]
Message-ID: <20100216200035.GA19834@inner.home.ulmdo.de> (raw)
In-Reply-To: <32541b131002160948h317e71f5m2d2cb839470a38f1@mail.gmail.com>
On Tue, 16 Feb 2010 12:48:16 +0000, Avery Pennarun wrote:
...
> Three suggestions I can offer:
...
> 2) Try using relative repo paths (like ../foo.git) in .gitmodules.
Is that a 'try', or are those supposed to work?
4) Use
[url "git@github.com:apk/"]
insteadOf = "git://github.com/apk/"
in ~/.gitconfig allows changing the the actual url used. I use that
to be able to clone seemingly with the public github url but still
be able to push. You can use that to let an submodule point to
some other place where there is a clone of the submodule repo,
or another access method.
Andreas
next prev parent reply other threads:[~2010-02-16 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 14:39 Git Submodule Usage Pattern Tim Visher
2010-02-16 17:48 ` Avery Pennarun
2010-02-16 20:00 ` Andreas Krey [this message]
2010-02-16 20:38 ` Avery Pennarun
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=20100216200035.GA19834@inner.home.ulmdo.de \
--to=a.krey@gmx.de \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=tim.visher@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).