All of lore.kernel.org
 help / color / mirror / Atom feed
* suggestion for git stash
@ 2007-09-30 18:50 Bruno Haible
  2007-09-30 19:59 ` Junio C Hamano
  0 siblings, 1 reply; 6+ messages in thread
From: Bruno Haible @ 2007-09-30 18:50 UTC (permalink / raw)
  To: git

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2007-09-30 22:30 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-09-30 18:50 suggestion for git stash Bruno Haible
2007-09-30 19:59 ` Junio C Hamano
2007-09-30 20:28   ` Matthieu Moy
2007-09-30 20:59   ` Bruno Haible
2007-09-30 21:29     ` Johannes Schindelin
2007-09-30 22:30       ` [PATCH] git stash: document apply's --index switch Miklos Vajna

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.