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

How to selectively recreate merge state?

From
Jay Soffian <jaysoffian@gmail.com>
Date
Dec 10, 2009, 23:56 UTC
Message-ID
<76718490912101556o3e2911e8t32b48c0b735fd98c@mail.gmail.com>
Let's say you initiate a merge:
$ git merge topic

And this merge results in conflicts in two files, foo and bar. You resolve the conflicts in both files, but then decide you don't like how you resolved bar.

How do you set the index and working-copy back to the state it was immediately after doing the merge for bar, while leaving the merge resolution alone for foo?

j.
Next: Junio C Hamano
Message 1 of 18 in “How to selectively recreate merge state?”
  1. Jay SoffianDec 10, 2009
  2. Junio C HamanoDec 11, 2009
  3. Jakub NarebskiDec 11, 2009
  4. Junio C HamanoDec 11, 2009
  5. Jakub NarebskiDec 11, 2009
  6. Michael J GruberDec 11, 2009
  7. Björn SteinbrinkDec 11, 2009
  8. Thomas RastDec 11, 2009
  9. Jakub NarebskiDec 11, 2009
  10. Michael J GruberDec 11, 2009
  11. Jakub NarebskiDec 11, 2009
  12. Michael J GruberDec 11, 2009
  13. Junio C HamanoDec 11, 2009
  14. Junio C HamanoDec 11, 2009
  15. Jay SoffianDec 11, 2009
  16. Junio C HamanoDec 11, 2009
  17. Paolo BonziniDec 11, 2009
  18. Junio C HamanoDec 11, 2009

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.