On Thu, Feb 13, 2020 at 10:55 AM Junio C Hamano <gitster@xxxxxxxxx> wrote: > IIUC, the simplest workflow using the new feature may go like this: > > $ edit file ;# edit a bit > $ git add file > $ edit file ;# even even more > $ git stash --cached > > After all of the above is done, "git stash list" may show that there > is a single stash that records the changes you made to the file > right after you added it, without your further changes (because you > are taking what is in the index). Your working tree has all the > changes you made to file, both before and after "git add", and your > index is clean. > > After you got yourself into this state where your index is clean, > your working tree file has all changes, and your stash entry has > only the earlier half of the change, what are you going to do with > that stash entry? If we learn the answer to that question, perhaps > we may find (or we may even have) a better or easier way to achieve > whatever you were planning to do with that stash entry by some other > means---it might not even involve "git stash"---but without knowing > that, we cannot tell if the new feature is a good idea. Actually, let this conversation burn in /dev/null. What I want to achieve (stash only some changes and not all of them) can be done by using git stash push providing pathspec. > > Thanks. Thank you!
