summaryrefslogtreecommitdiffstats
path: root/git-merge.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2021-12-15 13:00:31 -0800
committerJunio C Hamano <gitster@pobox.com>2021-12-15 13:00:31 -0800
commit2b15318a963a036b7d9b73e538c5ca566fec9794 (patch)
treeaee21ed0152eb1aefc8e8e2420de58a251d45b4b /git-merge.txt
parent59a32b07d3e226cad19135aee37bf81c8849efc8 (diff)
downloadgit-htmldocs-2b15318a963a036b7d9b73e538c5ca566fec9794.tar.gz
Autogenerated HTML docs for v2.34.1-297-g69a9c1
Diffstat (limited to 'git-merge.txt')
-rw-r--r--git-merge.txt32
1 files changed, 27 insertions, 5 deletions
diff --git a/git-merge.txt b/git-merge.txt
index e4f3352eb..e8cecf5a5 100644
--- a/git-merge.txt
+++ b/git-merge.txt
@@ -240,7 +240,8 @@ from the RCS suite to present such a conflicted hunk, like this:
------------
Here are lines that are either unchanged from the common
-ancestor, or cleanly resolved because only one side changed.
+ancestor, or cleanly resolved because only one side changed,
+or cleanly resolved because both sides changed the same way.
<<<<<<< yours:sample.txt
Conflict resolution is hard;
let's go shopping.
@@ -261,16 +262,37 @@ side wants to say it is hard and you'd prefer to go shopping, while the
other side wants to claim it is easy.
An alternative style can be used by setting the "merge.conflictStyle"
-configuration variable to "diff3". In "diff3" style, the above conflict
-may look like this:
+configuration variable to either "diff3" or "zdiff3". In "diff3"
+style, the above conflict may look like this:
------------
Here are lines that are either unchanged from the common
-ancestor, or cleanly resolved because only one side changed.
+ancestor, or cleanly resolved because only one side changed,
<<<<<<< yours:sample.txt
+or cleanly resolved because both sides changed the same way.
Conflict resolution is hard;
let's go shopping.
-|||||||
+||||||| base:sample.txt
+or cleanly resolved because both sides changed identically.
+Conflict resolution is hard.
+=======
+or cleanly resolved because both sides changed the same way.
+Git makes conflict resolution easy.
+>>>>>>> theirs:sample.txt
+And here is another line that is cleanly resolved or unmodified.
+------------
+
+while in "zdiff3" style, it may look like this:
+
+------------
+Here are lines that are either unchanged from the common
+ancestor, or cleanly resolved because only one side changed,
+or cleanly resolved because both sides changed the same way.
+<<<<<<< yours:sample.txt
+Conflict resolution is hard;
+let's go shopping.
+||||||| base:sample.txt
+or cleanly resolved because both sides changed identically.
Conflict resolution is hard.
=======
Git makes conflict resolution easy.