This is the first time I tried to do multi git stashes and it went horribly wrong because I did not understand how git stash works in this case.
My assumption and hope was that the "stash" was stored per branch. So when I would switch back to the branch where the "stash" was stored and I would do a "pop" it would come back. But instead it popped the wrong stash from another branch. That is what I think happened so far, after that it gets vague... I probably did another git stash trying to push it back or something. That is the part were it gets fuzy... since I pushed it back and such how were the changes lost ? Anyway I am tired of this stash confusion, I don't like how this functionality is implemented currently. Maybe later I will like it better. I did read up on git stash, apperently stashes can be applied to different branches. This is not the intended functionality that I had in mind when doing this... just wanted to store my changes on that branch AddThreadInfo and now they were horribly lost. An improvement to git would be to automatically add the branch name where the stash occured... I would like it better if stash would work the way I described, a "stack" per branch"... but ok... maybe in the future I might not like this.... Right now I don't see the point in having a stack that works across branches, this has huge potential for confusion. If I want to apply changes from other branches then there is git merge and such... Perhaps git merge could be extended to merge stashes changes on branches... that would make more sense to me. I am not amuzed, Bye, Skybuck =D -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/b26c1993-c40f-4803-8dcf-6bb36063049cn%40googlegroups.com.