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

[RFC] stash --continue

From
Stephan Beyer <s-beyer@gmx.net>
Date
Jan 15, 2017, 23:56 UTC
Message-ID
<cd784a4e-ee99-564e-81de-9f7f6cc26c67@gmx.net>
Hi,

a git-newbie-ish co-worker uses git-stash sometimes. Last time he used "git stash pop", he got into a merge conflict. After he resolved the conflict, he did not know what to do to get the repository into the wanted state. In his case, it was only "git add <resolved files>" followed by a "git reset" and a "git stash drop", but there may be more involved cases when your index is not clean before "git stash pop" and you want to have your index as before.

This led to the idea to have something like "git stash --continue"[1] that would expect the user to "git add" the resolved files (as "git status" suggests) but then leads to the expected result, i.e. the index being the same as before the conflict, the stash being dropped (if "pop" was used instead of "apply"), etc.

Likewise, some "git stash --abort"[2] might be useful in case you did "git stash pop" with the wrong stash in mind.

What do you think about that?

Although I think this would be a nice-to-have feature, I am not totally sure how to achieve backwards-compatibility, i.e., such that using --continue is still optional... (I think that "git stash apply" would surely generate auxiliary data in case of a conflict and --continue or --abort would remove it...)

Best
  Stephan
Footnotes
1. Perhaps with a better name, because it does not really continue.
Maybe a "git stash conflict [--resolved]" subcommand?
2. Along the lines of [1], one could use "git stash conflict --abort"?
Next: Jacob Keller
Message 1 of 16 in “[RFC] stash --continue”
  1. Stephan BeyerJan 15, 2017
  2. Jacob KellerJan 16, 2017
  3. Johannes SchindelinJan 16, 2017
  4. Marc BranchaudJan 18, 2017
  5. Johannes SchindelinJan 18, 2017
  6. Marc BranchaudJan 18, 2017
  7. Samuel LijinJan 18, 2017
  8. Johannes SchindelinJan 19, 2017
  9. Marc BranchaudJan 19, 2017
  10. Johannes SchindelinJan 19, 2017
  11. Marc BranchaudJan 20, 2017
  12. Johannes SchindelinJan 20, 2017
  13. Junio C HamanoJan 18, 2017
  14. Stephan BeyerJan 18, 2017
  15. Johannes SchindelinJan 19, 2017
  16. Junio C HamanoJan 17, 2017

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.