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

[PATCHv2] rerere.txt: Document forget subcommand

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Jul 5, 2010, 13:15 UTC
Message-ID
<4d2171a1aeb40321f5956da48f2a36e7709a8a7c.1278333908.git.git@drmicha.warpmail.net>
In-Reply-To
<7vljaeg9wt.fsf@alter.siamese.dyndns.org>

dea4562 (rerere forget path: forget recorded resolution, 2009-12-25) introduced the forget subcommand for rerere.

Document it.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
This somewhat fell under all radars.
v2 takes into account suggestions by Junio and Jay.
 Documentation/git-rerere.txt |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-rerere.txt b/Documentation/git-rerere.txt
index acc220a..db99d47 100644
--- a/Documentation/git-rerere.txt
+++ b/Documentation/git-rerere.txt
@@ -7,7 +7,7 @@ git-rerere - Reuse recorded resolution of conflicted merges
 
 SYNOPSIS
 --------
-'git rerere' ['clear'|'diff'|'status'|'gc']
+'git rerere' ['clear'|'forget' [<pathspec>]|'diff'|'status'|'gc']
 
 DESCRIPTION
 -----------
@@ -40,6 +40,11 @@ This resets the metadata used by rerere if a merge resolution is to be
 aborted.  Calling 'git am [--skip|--abort]' or 'git rebase [--skip|--abort]'
 will automatically invoke this command.
 
+'forget' <pathspec>::
+
+This resets the conflict resolutions which rerere has recorded for the current
+conflict in <pathspec>.  The <pathspec> is optional.
+
 'diff'::
 
 This displays diffs for the current state of the resolution.  It is
-- 
1.7.1.621.g01d76
Previous: Junio C HamanoNext: Johannes Sixt
Message 7 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.