From: Andreas Schwab <schwab@linux-m68k.org>
To: Eyal Lotem <eyal.lotem@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: BUG: Renaming a branch checked out in a different work tree
Date: Wed, 29 Mar 2017 20:43:52 +0200 [thread overview]
Message-ID: <87d1czditz.fsf@linux-m68k.org> (raw)
In-Reply-To: <CALA94fPqm5UnYBwqZ5fDJ=DL_9EaZeRfqHB5ZzUQt11FSz4ZMA@mail.gmail.com> (Eyal Lotem's message of "Wed, 29 Mar 2017 21:02:10 +0300")
On Mär 29 2017, Eyal Lotem <eyal.lotem@gmail.com> wrote:
> git version: 2.7.4
> installed from Ubuntu repos:
> Ubuntu Version: 1:2.7.4-0ubuntu1
>
> When renaming a branch checked out in a different work tree, that work
> tree's state is corrupted. Git status in that work tree then reports
> itself being on the "initial commit" with all files being in the
> staging area.
Fixed since 2.8.3.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2017-03-29 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 18:02 BUG: Renaming a branch checked out in a different work tree Eyal Lotem
2017-03-29 18:40 ` Jonathan Nieder
2017-03-29 18:43 ` Andreas Schwab [this message]
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=87d1czditz.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=eyal.lotem@gmail.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).