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

[PATCH] Documentation/git-rerere: document 'remaining' command

From
Vincent van Ravesteijn <vfr@lyx.org>
Date
Mar 6, 2012, 12:21 UTC
Message-ID
<1331036512-7626-1-git-send-email-vfr@lyx.org>
From: Vincent van Ravesteijn <vfr@lyx.org>

This adds the 'remaining' command to the documentation of 'git rerere'. This command was added in ac49f5ca (Feb 16 2011; Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>) but it was never documented.

Signed-off-by: Vincent van Ravesteijn <vfr@lyx.org>
---
 Documentation/git-rerere.txt |   10 +++++++++-
 1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-rerere.txt b/Documentation/git-rerere.txt
index a6253ba..b75d34b 100644
--- a/Documentation/git-rerere.txt
+++ b/Documentation/git-rerere.txt
@@ -8,7 +8,7 @@ git-rerere - Reuse recorded resolution of conflicted merges
 SYNOPSIS
 --------
 [verse]
-'git rerere' ['clear'|'forget' <pathspec>|'diff'|'status'|'gc']
+'git rerere' ['clear'|'forget' <pathspec>|'diff'|'remaining'|'status'|'gc']
 
 DESCRIPTION
 -----------
@@ -53,6 +53,14 @@ useful for tracking what has changed while the user is resolving
 conflicts.  Additional arguments are passed directly to the system
 'diff' command installed in PATH.
 
+'remaining'::
+
+Like 'diff', but this only prints the unresolved filenames. This
+includes the files for which rerere tracks the resolution (as shown
+by 'git rerere status'), but also the files for which the conflicts
+cannot be tracked by rerere, e.g. files with conflicts that do not 
+have both our side and their side like "we modified, they deleted".
+
 'status'::
 
 Like 'diff', but this only prints the filenames that will be tracked
-- 
1.7.5.4
Next: Junio C Hamano
Message 1 of 8 in “Documentation/git-rerere: document 'remaining' command”
  1. Documentation/git-rerere: document 'remaining' commandVincent van Ravesteijn, Mar 6, 2012
  2. Junio C HamanoMar 6, 2012
  3. Phil HordMar 7, 2012
  4. Junio C HamanoMar 7, 2012
  5. Phil HordMar 8, 2012
  6. Junio C HamanoMar 8, 2012
  7. Phil HordMar 8, 2012
  8. Junio C HamanoMar 8, 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.