From: Jonathan Nieder <jrnieder@gmail.com>
To: Manish Gill <mgill25@outlook.com>
Cc: git@vger.kernel.org, "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: Problem switching branches in submodule
Date: Thu, 26 Sep 2013 11:08:52 -0700 [thread overview]
Message-ID: <20130926180852.GF9464@google.com> (raw)
In-Reply-To: <BLU0-SMTP17403D5452DA1619FEFCCBAB8280@phx.gbl>
(cc-ing Duy, who knows the setup code well)
Manish Gill wrote:
> I have a git repository with lots of submodules. In one particular
> submodule, I'm having the following problem:
>
> If I try to switch branches at the top-level of that submodule, I succeed.
>
> But, if I try to switch branches in any subsequen levels, I get the
> following error:
>
> fatal: internal error: work tree has already been set
> Current worktree: ../path/Mailman3/rest_project
> New worktree: ../path/Mailman3/rest_project/website/public_rest
>
> Here, Mailman3 is the primary repository and "rest_project" is a
> submodule. I can do "git checkout" just fine
> inside rest_project, but not after cd-ing into any other repos.
>
> My git version is 1.8.4
>
> Other commands, like git status, push/pull are working fine.
Interesting. Yeah, this shouldn't happen.
What is the exact command you use to get the above output? Is your
repository public (which would let us reproduce it) or can you
reproduce it by creating a small artificial test repository?
For comparison, did some previous version of git work ok in the same
scenario, or is this the first time you've tried it?
Thanks,
Jonathan
next prev parent reply other threads:[~2013-09-26 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 17:20 Problem switching branches in submodule Manish Gill
2013-09-26 18:08 ` Jonathan Nieder [this message]
2013-09-26 18:33 ` Manish Gill
2013-09-26 18:48 ` Jonathan Nieder
2013-09-26 19:29 ` Manish Gill
2013-09-26 23:44 ` Duy Nguyen
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=20130926180852.GF9464@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=mgill25@outlook.com \
--cc=pclouds@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).