{"thread":{"id":"45539","subject":"BUG: Renaming a branch checked out in a different work tree","startedAt":"2017-03-29T18:02:31Z","lastAt":"2017-03-29T18:44:00Z","messageCount":3,"participants":["Eyal Lotem","Jonathan Nieder","Andreas Schwab"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"315693","messageId":"CALA94fPqm5UnYBwqZ5fDJ=DL_9EaZeRfqHB5ZzUQt11FSz4ZMA@mail.gmail.com","threadId":"45539","inReplyTo":null,"subject":"BUG: Renaming a branch checked out in a different work tree","fromName":"Eyal Lotem","fromEmail":"eyal.lotem@gmail.com","sentAt":"2017-03-29T18:02:10Z","receivedAt":"2017-03-29T18:02:31Z","isPatch":false,"sender":{"key":"eyal.lotem@gmail.com","avatar":null},"body":"git version: 2.7.4\ninstalled from Ubuntu repos:\nUbuntu Version: 1:2.7.4-0ubuntu1\n\nWhen renaming a branch checked out in a different work tree, that work\ntree's state is corrupted. Git status in that work tree then reports\nitself being on the \"initial commit\" with all files being in the\nstaging area.\n\n--\nEyal\n"},{"id":"315697","messageId":"20170329184018.GV31294@aiede.mtv.corp.google.com","threadId":"45539","inReplyTo":"CALA94fPqm5UnYBwqZ5fDJ=DL_9EaZeRfqHB5ZzUQt11FSz4ZMA@mail.gmail.com","subject":"Re: BUG: Renaming a branch checked out in a different work tree","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2017-03-29T18:40:18Z","receivedAt":"2017-03-29T18:40:27Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"(+cc: Kazuki Yamaguchi --- thanks for writing the fix!)\nHi Eyal,\n\nEyal Lotem wrote:\n\n> git version: 2.7.4\n> installed from Ubuntu repos:\n> Ubuntu Version: 1:2.7.4-0ubuntu1\n>\n> When renaming a branch checked out in a different work tree, that work\n> tree's state is corrupted. Git status in that work tree then reports\n> itself being on the \"initial commit\" with all files being in the\n> staging area.\n\nI believe this is fixed by v2.8.3~42^2~1 (branch -m: update all\nper-worktree HEADs, 2016-03-27).\n\nThanks and hope that helps,\nJonathan\n"},{"id":"315698","messageId":"87d1czditz.fsf@linux-m68k.org","threadId":"45539","inReplyTo":"CALA94fPqm5UnYBwqZ5fDJ=DL_9EaZeRfqHB5ZzUQt11FSz4ZMA@mail.gmail.com","subject":"Re: BUG: Renaming a branch checked out in a different work tree","fromName":"Andreas Schwab","fromEmail":"schwab@linux-m68k.org","sentAt":"2017-03-29T18:43:52Z","receivedAt":"2017-03-29T18:44:00Z","isPatch":false,"sender":{"key":"schwab@linux-m68k.org","avatar":"https://avatars.githubusercontent.com/u/2175493?v=4"},"body":"On Mär 29 2017, Eyal Lotem <eyal.lotem@gmail.com> wrote:\n\n> git version: 2.7.4\n> installed from Ubuntu repos:\n> Ubuntu Version: 1:2.7.4-0ubuntu1\n>\n> When renaming a branch checked out in a different work tree, that work\n> tree's state is corrupted. Git status in that work tree then reports\n> itself being on the \"initial commit\" with all files being in the\n> staging area.\n\nFixed since 2.8.3.\n\nAndreas.\n\n-- \nAndreas Schwab, schwab@linux-m68k.org\nGPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5\n\"And now for something completely different.\"\n"}]}