{"thread":{"id":"24343","subject":"Git stash bug","startedAt":"2010-07-09T05:35:28Z","lastAt":"2010-07-09T12:15:16Z","messageCount":2,"participants":["Anirban Mitra"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"145194","messageId":"4C36B520.70105@directi.com","threadId":"24343","inReplyTo":null,"subject":"Git stash bug","fromName":"Anirban Mitra","fromEmail":"anirban.m@directi.com","sentAt":"2010-07-09T05:35:28Z","receivedAt":"2010-07-09T05:35:28Z","isPatch":false,"sender":{"key":"anirban.m@directi.com","avatar":null},"body":"Hi,\n\nI ran into a git stash bug. I added a new project config file used by \nthe IDE in a commit and later reverted the commit. But the same file \nagain created by the IDE and now when I use git stash that file changes \nare also stashed. When I try stash pop, it complains that the file will \nbe overwritten and aborts.\n\nI did not expect this because I have reverted the commit adding the \nfile. Is it intended behaviour? Am I missing something or is this a \nknown bug and will be fixed in later releases? I am using Git version \n1.7.0.4.\n\n-- Anirban\n"},{"id":"145207","messageId":"4C3712D4.8020909@directi.com","threadId":"24343","inReplyTo":"4C36B520.70105@directi.com","subject":"Re: Git stash bug","fromName":"Anirban Mitra","fromEmail":"anirban.m@directi.com","sentAt":"2010-07-09T12:15:16Z","receivedAt":"2010-07-09T12:15:16Z","isPatch":false,"sender":{"key":"anirban.m@directi.com","avatar":null},"body":"Hi,\n\nSorry for the last msg. It seems the behavior happened in a different \nsituation then what I described which now I can't reproduce.\n\n-- Anirban\n\nOn Friday 09 July 2010 11:05 AM, Anirban Mitra wrote:\n> Hi,\n>\n> I ran into a git stash bug. I added a new project config file used by \n> the IDE in a commit and later reverted the commit. But the same file \n> again created by the IDE and now when I use git stash that file \n> changes are also stashed. When I try stash pop, it complains that the \n> file will be overwritten and aborts.\n>\n> I did not expect this because I have reverted the commit adding the \n> file. Is it intended behaviour? Am I missing something or is this a \n> known bug and will be fixed in later releases? I am using Git version \n> 1.7.0.4.\n>\n> -- Anirban\n"}]}