From d4cbaa12a774a97dfa9e99aad9188dc802469bb6 Mon Sep 17 00:00:00 2001 From: Thomas Rast Date: Sun, 15 Nov 2009 19:25:30 +0100 Subject: [PATCH] Documentation: clarify 'ours' merge strategy Make it clear in the docs that the merge takes the tree of HEAD and ignores everything in the other branches. This should hopefully clear up confusion, usually caused by the user looking for a strategy that resolves all conflict hunks in favour of HEAD (which is completely different and currently not supported). Signed-off-by: Thomas Rast Signed-off-by: Junio C Hamano --- Documentation/merge-strategies.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/merge-strategies.txt b/Documentation/merge-strategies.txt index 4365b7e84..42910a3d5 100644 --- a/Documentation/merge-strategies.txt +++ b/Documentation/merge-strategies.txt @@ -29,8 +29,9 @@ octopus:: pulling or merging more than one branch. ours:: - This resolves any number of heads, but the result of the - merge is always the current branch head. It is meant to + This resolves any number of heads, but the resulting tree of the + merge is always that of the current branch head, effectively + ignoring all changes from all other branches. It is meant to be used to supersede old development history of side branches. -- 2.26.2