diff options
| author | Junio C Hamano <gitster@pobox.com> | 2018-09-17 13:53:56 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2018-09-17 13:53:57 -0700 |
| commit | d88949d86eddb62acbc85c16c97587db043d05b1 (patch) | |
| tree | da1257a2fbea26867cd6226c308cfd9004db81bb /Documentation/technical | |
| parent | 881c019ea6a0a45f97fb8a1865a88b07263a02ca (diff) | |
| parent | f427869bde759e32c30e8ba7a4b20837d3806642 (diff) | |
| download | git-d88949d86eddb62acbc85c16c97587db043d05b1.tar.gz | |
Merge branch 'tg/rerere-doc-updates'
Clarify a part of technical documentation for rerere.
* tg/rerere-doc-updates:
rerere: add note about files with existing conflict markers
rerere: mention caveat about unmatched conflict markers
Diffstat (limited to 'Documentation/technical')
| -rw-r--r-- | Documentation/technical/rerere.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/technical/rerere.txt b/Documentation/technical/rerere.txt index e65ba9b0c6..aa22d7ace8 100644 --- a/Documentation/technical/rerere.txt +++ b/Documentation/technical/rerere.txt @@ -149,6 +149,10 @@ version, and the sorting the conflict hunks, both for the outer and the inner conflict. This is done recursively, so any number of nested conflicts can be handled. +Note that this only works for conflict markers that "cleanly nest". If +there are any unmatched conflict markers, rerere will fail to handle +the conflict and record a conflict resolution. + The only difference is in how the conflict ID is calculated. For the inner conflict, the conflict markers themselves are not stripped out before calculating the sha1. |