From: "W. Trevor King" <wking@tremily.us>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Jonathan Nieder <jrnieder@gmail.com>, Git <git@vger.kernel.org>,
Peter Collingbourne <peter@pcc.me.uk>
Subject: Re: Moving (renaming) submodules, recipe/script
Date: Tue, 08 Jan 2013 10:59:32 -0500 [thread overview]
Message-ID: <20130108155932.GB4662@odin.tremily.us> (raw)
In-Reply-To: <20130108143214.GA3755@odin.tremily.us> <20121023220955.GA30442@odin.tremily.us>
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-08 16:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 12:37 Git submodule for a local branch? W. Trevor King
2012-10-23 13:21 ` W. Trevor King
2012-10-23 20:57 ` Jens Lehmann
2012-10-23 22:09 ` W. Trevor King
2013-01-08 15:59 ` W. Trevor King [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-07 0:36 Moving (renaming) submodules, recipe/script W. Trevor King
2013-01-07 1:39 ` Jonathan Nieder
2013-01-07 6:59 ` Jens Lehmann
2013-01-07 7:44 ` Junio C Hamano
2013-01-07 8:18 ` Jens Lehmann
2013-01-07 16:08 ` Junio C Hamano
2013-01-07 12:08 ` W. Trevor King
2013-01-08 14:32 ` W. Trevor King
2013-01-08 17:12 ` Jens Lehmann
2013-01-08 17:48 ` W. Trevor King
2013-02-09 12:32 ` [BUG] can't switch branches with submodules W. Trevor King
2013-02-03 23:38 ` Moving (renaming) submodules, recipe/script W. Trevor King
2013-02-03 22:36 [New Feature] git-submodule-move - Easily move submodules TJ
2013-02-04 20:14 ` Jens Lehmann
2013-02-09 12:25 [BUG] can't switch branches with submodules Ramkumar Ramachandra
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130108155932.GB4662@odin.tremily.us \
--to=wking@tremily.us \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peter@pcc.me.uk \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).