Hi, "git stash" has the effect of losing the distinction between untracked changes and changes in the index. To reproduce: - Clone the gnulib repository or of any repository with at least 2 files. - Make changes to two files, say, README and NEWS. $ git add README - $ git status now reports: # On branch master # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # modified: README # # Changed but not updated: # (use "git add <file>..." to update what will be committed) # # modified: NEWS # - $ git stash - $ git stash apply - $ git status now reports: # On branch master # Changed but not updated: # (use "git add <file>..." to update what will be committed) # # modified: NEWS # modified: README # no changes added to commit (use "git add" and/or "git commit -a") Could "git stash" be changed to memorize which changes were already scheduled for commit and which didn't? Bruno - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
