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

Re: Edit a rerere conflict resolution

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 16, 2012, 16:01 UTC
Message-ID
<7vaa3gilg7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4F636227.2060102@lyx.org>
Vincent van Ravesteijn <vfr@lyx.org> writes:
Show 34 quoted lines
> Op 12-3-2012 21:01, Junio C Hamano schreef:
> ...
>> I haven't find it necessary in practice, as the re-fix for me
>> typically would go like this:
>>
>>      $ git merge other-branch
>>      ... rerere kicks in; eyeball the results
>>      ... ah, my earlier resolution is no longer correct
>>      $ edit $the_path
>>      ... test the result of manual edit in the context of the merged whole
>>      ... and be satisified
>>      $ git rerere forget $the_path
>>      $ git add $the_path
>>      $ git commit
>>      ... rerere records the updated resolution
>>
> This doesn't really work for me:
>
>      $ git merge other-branch
>      Auto-merging <path>
>      CONFLICT (content): Merge conflicts in <path>
>      Resolved '<path>' using previous resolution.
>      Automatic merge failed; fix conflicts and then commit the result.
>
>      $ git rerere status
>      $ git rerere forget <path>
>      error: no remembered resolution for <path>
>
>      $ edit <path>
>      $ git commit -a -m "fix"
>      ... no sign of rerere doing something.
>
> Why is this different from what you describe above, and how can I
> modify the recorded resolution ?

Do you have rerere.autoupdate set by any chance? If so, don't. At least when you are trying to purge the broken rerere entry.

Previous: Vincent van RavesteijnNext: Vincent van Ravesteijn
Message 11 of 16 in “Edit a rerere conflict resolution”
  1. Vincent van RavesteijnMar 12, 2012
  2. Junio C HamanoMar 12, 2012
  3. Vincent van RavesteijnMar 12, 2012
  4. Junio C HamanoMar 12, 2012
  5. Vincent van RavesteijnMar 12, 2012
  6. Junio C HamanoMar 12, 2012
  7. Vincent van RavesteijnMar 12, 2012
  8. Jakub NarebskiMar 12, 2012
  9. Junio C HamanoMar 12, 2012
  10. Vincent van RavesteijnMar 16, 2012
  11. Junio C HamanoMar 16, 2012
  12. Vincent van RavesteijnMar 16, 2012
  13. Junio C HamanoMar 16, 2012
  14. Vincent van RavesteijnMar 16, 2012
  15. Junio C HamanoMar 16, 2012
  16. Vincent van RavesteijnMar 17, 2012

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.