diff options
author | Elijah Newren <newren@gmail.com> | 2021-12-01 03:05:07 +0300 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2021-12-02 01:45:59 +0300 |
commit | ddfc44a898a58311392a5329687a1813d6b94779 (patch) | |
tree | b264cec304adc063f1f186bd799bebacc03edf53 /Documentation/git-rebase.txt | |
parent | 4496526f80b3e4952036550b279eff8d1babd60a (diff) |
update documentation for new zdiff3 conflictStyle
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-rebase.txt')
-rw-r--r-- | Documentation/git-rebase.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt index a1af21fcef..9da4647061 100644 --- a/Documentation/git-rebase.txt +++ b/Documentation/git-rebase.txt @@ -714,9 +714,9 @@ information about the rebased commits and their parents (and instead generates new fake commits based off limited information in the generated patches), those commits cannot be identified; instead it has to fall back to a commit summary. Also, when merge.conflictStyle is -set to diff3, the apply backend will use "constructed merge base" to -label the content from the merge base, and thus provide no information -about the merge base commit whatsoever. +set to diff3 or zdiff3, the apply backend will use "constructed merge +base" to label the content from the merge base, and thus provide no +information about the merge base commit whatsoever. The merge backend works with the full commits on both sides of history and thus has no such limitations. |