On Tue, Jan 08, 2013 at 09:32:14AM -0500, W. Trevor King wrote: > Thinking about this a bit more, I'm not clear on how out-of-tree > updates (i.e. worktree in .git/modules/*/config) propogated during > branch checkouts (merges, rebases, etc.).
Actually, I don't understand why storing `worktree` in .git/modules/*/config is useful at all…. This may be related to my lack of clarity on the "why can't we have multiple working directories checked out at the same time" issue: On Tue, Oct 23, 2012 at 06:09:55PM -0400, W. Trevor King wrote: > On Tue, Oct 23, 2012 at 10:57:57PM +0200, Jens Lehmann wrote: > > Am 22.10.2012 14:37, schrieb W. Trevor King: > > > but cloning a remote repository (vs. checking out a local branch) > > > seems to be baked into the submodule implementation. Should I be > > > thinking about generalizing git-submodule.sh, or am I looking under > > > the wrong rock? My ideal syntax would be something like > > > > > > $ git submodule add -b c --local dir-for-c/ > > > > But then we'd have to be able to have two (or more) work trees using > > the same git directory, which current submodule code can't. > > And that's the problem I'm trying to solve ;). Can someone with a better feeling for why this won't work. Is is just that there's only one `.git/HEAD`? Cheers, Trevor -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
Description: OpenPGP digital signature