{"thread":{"id":"34779","subject":"Asymmetric default behavior of git stash","startedAt":"2013-08-27T14:07:09Z","lastAt":"2013-08-27T14:07:09Z","messageCount":1,"participants":["Uwe Storbeck"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"225992","messageId":"20130827132210.GA14266@ibr.ch","threadId":"34779","inReplyTo":null,"subject":"Asymmetric default behavior of git stash","fromName":"Uwe Storbeck","fromEmail":"uwe@ibr.ch","sentAt":"2013-08-27T14:07:09Z","receivedAt":"2013-08-27T14:07:09Z","isPatch":false,"sender":{"key":"uwe@ibr.ch","avatar":null},"body":"Hi,\n\nis there any reason why the default behavior of git stash is\nasymmetric?\n\nWhen I save my current state with 'git stash save' it saves the\nworktree changes and the index changes (and resets both). When I\nrestore the state with 'git stash pop' it restores the worktree\nchanges, but not the state of the index. Your work preparing the\nindex is lost.\n\nAlthough this behavior is documented it is kind of unexpected.\nFrom a save-restore mechanism I would expect that the default\nbehavior would restore the state as it was before the save. So\nI would expect it to either save and restore the worktree and\nleave the index alone or save and restore both, the worktree\nand the index.\n\nRegards\n\nUwe\n"}]}