On 9/5/21 10:15 AM, Chris Torek wrote:
It does,*provided* you invoke the pop step with `--index`. When `git stash push` makes a stash, it saves both the index (staging area) and working tree, as two separate commits.
Why 'stash push' and 'stash pop' are asymmetric in what they do by default?Wouldn't it make more sense to make 'stash pop' precisely revert what 'stash push' does, and have an option '--no-index' instead?
Yuri