Skip to content

Commit

Permalink
Merge branch 'ph/rerere-doc' into maint-1.7.8
Browse files Browse the repository at this point in the history
* ph/rerere-doc:
  rerere: Document 'rerere remaining'
  • Loading branch information
Junio C Hamano committed Apr 9, 2012
2 parents d4c813d + 3e7a1df commit dbdc07f
Showing 1 changed file with 12 additions and 7 deletions.
19 changes: 12 additions & 7 deletions Documentation/git-rerere.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
-----------
Expand Down Expand Up @@ -37,30 +37,35 @@ its working state.

'clear'::

This resets the metadata used by rerere if a merge resolution is to be
Reset 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
Reset the conflict resolutions which rerere has recorded for the current
conflict in <pathspec>.

'diff'::

This displays diffs for the current state of the resolution. It is
Display diffs for the current state of the resolution. It is
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.

'status'::

Like 'diff', but this only prints the filenames that will be tracked
for resolutions.
Print paths with conflicts whose merge resolution rerere will record.

'remaining'::

Print paths with conflicts that have not been autoresolved by rerere.
This includes paths whose resolutions cannot be tracked by rerere,
such as conflicting submodules.

'gc'::

This prunes records of conflicted merges that
Prune records of conflicted merges that
occurred a long time ago. By default, unresolved conflicts older
than 15 days and resolved conflicts older than 60
days are pruned. These defaults are controlled via the
Expand Down

0 comments on commit dbdc07f

Please sign in to comment.