git/list[1] front-page[2] threads[3] people[4] search[5] about
 

How to resolve git stash conflict without adding to index?

From
SBSven Bachmann <dev@mcbachmann.de>
Date
Nov 8, 2011, 09:10 UTC
Message-ID
<20111108101004.Horde.46VbWsL8999OuPHsJOQ2ZrA@webmail.df.eu>
Hi Git-Group,

from time to time I've got to "git stash" a bunch of files (about 20). My problem is, sometimes "git stash pop" conflicts and all files are added to the index - which is not what I want.

I just want to have the same behavior like "git stash pop" without conflict has. Resolving the conflict is okay, but not "git reset HEAD" to all other files, which I don't want to commit now.

Is there a possibility that "git stash pop" does not add all files to the index when a conflict appears?

I've already asked this question on stackoverflow ( http://stackoverflow.com/questions/7751555/how-to-resolve-git-stash-conflict-without-commit ) - maybe this helps a bit better to describe the problem.

Please add me to CC if possible as I'm not subscribed to this list and reading it in the browser.

Thanks a lot in advance!
   Sven
Message 1 of 1 in “How to resolve git stash conflict without adding to index?”
  1. Sven BachmannNov 8, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.