From: Avery Pennarun <apenwarr@gmail.com>
To: Andreas Krey <a.krey@gmx.de>
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 15:38:36 -0500 [thread overview]
Message-ID: <32541b131002161238h5549882fv89ab90812b3e8131@mail.gmail.com> (raw)
In-Reply-To: <20100216200035.GA19834@inner.home.ulmdo.de>
On Tue, Feb 16, 2010 at 3:00 PM, Andreas Krey <a.krey@gmx.de> wrote:
> 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?
It works. The reason I said "try" is that in order to *make* it work,
you may have to move your repositories around so that you can reach
one using a relative path from the other (ie. it's easiest if they're
on the same server at the same level of the directory hierarchy).
Avery
prev parent reply other threads:[~2010-02-16 20:39 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
2010-02-16 20:38 ` Avery Pennarun [this message]
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=32541b131002161238h5549882fv89ab90812b3e8131@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=a.krey@gmx.de \
--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).