# git stash merge 2 messages from 2015-04-20 to 2015-04-20. Participants: Pawel Por, Junio C Hamano. Thread: https://gitlist.dev/t/39119 ## Pawel Por, 2015-04-20 16:36 Subject: git stash merge Message-ID: URL: https://gitlist.dev/e/CAJmOuEwEgA-9NCtBXjij-rLhsCWMyw%2BDcRVGo4%3D0b1V2nC%3D%3DcA%40mail.gmail.com ``` Hi, I've just upgraded the linux kernel git source tree and I want to "pop" my stashed work. I do the following: git stash pop and I got the following message: mm/Makefile: needs merge unable to refresh index I also tried: git stash pop --index How can I overcome this obstacle. I did "git stash" before "git pull". Thanks for help. ``` ## Junio C Hamano, 2015-04-20 18:12 Subject: Re: git stash merge Message-ID: URL: https://gitlist.dev/e/xmqqy4lmllct.fsf%40gitster.dls.corp.google.com In-Reply-To: ``` Pawel Por writes: > I've just upgraded the linux kernel git source tree and I want to > "pop" my stashed work. I do the following: > git stash pop > > and I got the following message: > mm/Makefile: needs merge > unable to refresh index The symptom indicates that "upgraded the linux kernel git source tree" has not been cleanly completed and has an unmerged entry in the index. That is the first thing "stash pop" tries to check that the source tree does not have any pending change that does not have anything to do with your application of the stash, and you seem to be triggering that safety check. If your working tree does not have changes of any value, perhaps "git reset --hard && git pull" (or you may even want to resort to "git fetch && git reset --hard origin") to make sure "upgraded the source tree" part truly has cleanly completed may be a good second step to get "stash pop" going. The good first step is to see what local changes you have, of course---perhaps your "upgraded the linux kernel git source tree" conflicted with your local changes that you need to resolve first. ```