git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: Tim Visher <tim.visher@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Git Submodule Usage Pattern
Date: Tue, 16 Feb 2010 12:48:16 -0500	[thread overview]
Message-ID: <32541b131002160948h317e71f5m2d2cb839470a38f1@mail.gmail.com> (raw)
In-Reply-To: <c115fd3c1002160639m113a3604wa6686bc613a7c202@mail.gmail.com>

On Tue, Feb 16, 2010 at 9:39 AM, Tim Visher <tim.visher@gmail.com> wrote:
> Apparently, submodules are not configured on a per-repo basis, unless
> I'm totally misunderstanding something.  The .gitmodules file wants to
> be checked in just like .gitignore, etc.  I don't know if submodules
> will work correctly without syncing that between repos, either.  What
> I need is to have the submodule at work point at a different repo than
> the submodule at Home to avoid firewall issues.  Or for someone to
> suggest a different work flow that would allow me to have my main home
> repo point at GitHub using my private git:// address and the
> zen-and-art repo using it's public git:// clone address and then have
> my Work repo clone from GitHub around the firewall (or somewhere else,
> GitHub's http cloning is still pretty Janky) but then push to the
> Stick.

Three suggestions I can offer:

1) After running 'git submodule init', look in .git/config.  You can
change which repos the submodules point to from there, on a per-repo
basis, and not affect other people's checkouts.

2) Try using relative repo paths (like ../foo.git) in .gitmodules.
Then as long as your repositories are siblings of each other, if you
can check out one you can check out the other.

3) git-subtree (http://github.com/apenwarr/git-subtree) does not
exhibit this problem.

Have fun,

Avery

  reply	other threads:[~2010-02-16 17:48 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 [this message]
2010-02-16 20:00   ` Andreas Krey
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=32541b131002160948h317e71f5m2d2cb839470a38f1@mail.gmail.com \
    --to=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).