Sergey Organov <sorganov@xxxxxxxxx> writes: > I didn't ask you what --staged is suitable for, sorry. I asked how do > you solve the problem of saving an *entirely unrelated* subset of > changes for future use? Ah, OK. I do not think I would "git add" unrelated pieces in the first place, so "add -p && stash --staged" as a way to stash away such a change would be quite foreign concept in my workflow. IOW, I'd concentrate on finishing the step I am working on, leaving unrelated changes in the working tree, and when I came to a good stopping point, I'd do the "stash -k && test && commit" dance, followed by "stash pop". At that point,the working tree would have only unrelated changes that I can stash away with "stash save". So I guess perhaps your "no such problem for me" is the closest? Thanks.
