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

Re: Amending a merge commit doesn't update the rerere cache

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Jun 15, 2010, 06:23 UTC
Message-ID
<4C171C7B.3060904@viscovery.net>
In-Reply-To
<AANLkTik50ayTQUnft4oD0Paqf-AuFWxGNdx_zZlHKFPg@mail.gmail.com>
Am 6/15/2010 1:04, schrieb Jay Soffian:
Show 5 quoted lines
> Subject says it all, but I'll elaborate.
> 
> During the course of testing a merge, I'll sometimes realize there was
> a mistake and I'll amend the merge commit. Sadly this doesn't update
> the rerere cache.
There is
	git rerere forget that/conflicted/file

It definitely works as long as the conflict is still recorded in the index; I'm not sure if it works after you have staged the updated resolution.

-- Hannes
Previous: Michael J GruberNext: Jay Soffian
Message 8 of 9 in “Amending a merge commit doesn't update the rerere cache”
  1. Jay SoffianJun 14, 2010
  2. rerere.txt: Document forget subcommandMichael J Gruber, Jun 15, 2010
  3. Junio C HamanoJun 15, 2010
  4. Jay SoffianJun 15, 2010
  5. Michael J GruberJun 16, 2010
  6. Junio C HamanoJun 16, 2010
  7. [PATCHv2] rerere.txt: Document forget subcommandMichael J Gruber, Jul 5, 2010
  8. Johannes SixtJun 15, 2010
  9. Jay SoffianJun 15, 2010

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.