git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Wong <andrew.w@sohovfx.com>
To: git@vger.kernel.org
Subject: How to manage multiple repos using submodules?
Date: Sat, 16 Apr 2011 12:45:27 -0400	[thread overview]
Message-ID: <4DA9C7A7.4010503@sohovfx.com> (raw)

It seems like submodule isn't meant for this, but many people seems to 
use submodule to link many smaller repos together. With this setup, I 
imagine whenever someone pushed a small repo, they're /supposed/ to push 
the big repo as well. This way, if I simply update the big repo and do a 
"git status", git will tell me that which of the smaller repos are out 
of date. However, this is only reliable if everyone remembers to push 
the big repo. If someone pushed a smaller repo, but forgot to push the 
big repo, then I won't be aware that some of the smaller repos are 
out-of-date until I push.

I suppose one way is to do a check/auto-update with pre/post commit 
script to enforce that the big repo is always up-to-date. Another way is 
to use the "submodule foreach" to do a fetch and status on smaller ones, 
but this doesn't seem very elegant.

So, I'm wondering how do people who use submodules this way manage all 
their repos? Or how to (reliably) get a good sense of the state of the 
small repos? Or maybe I shouldn't be using submodules this way at all?

             reply	other threads:[~2011-04-16 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16 16:45 Andrew Wong [this message]
2011-04-16 18:20 ` How to manage multiple repos using submodules? Jonathan Nieder
2011-04-17  6:48   ` Jonathan Nieder
2011-04-17 18:42     ` Andrew Wong
2011-04-19 13:18   ` Phil Hord

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=4DA9C7A7.4010503@sohovfx.com \
    --to=andrew.w@sohovfx.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).