Documentation: merge-output is not too verbose now.
authorJunio C Hamano <junkio@cox.net>
Mon, 15 Jan 2007 05:31:30 +0000 (21:31 -0800)
committerJunio C Hamano <junkio@cox.net>
Mon, 15 Jan 2007 05:31:30 +0000 (21:31 -0800)
We've squelched output from merge-recursive, and git-merge when
used with recursive does not attempt the trivial one first
anymore, so there won't be "Trying ... Nope." messages now.

Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/core-tutorial.txt
Documentation/git-reset.txt
index 51dd6c6164c3b2a7026f33e59137a611e3929c32..7317489cfcdda369e7e296ff9032c36848efe11e 100644 (file)
@@ -906,18 +906,13 @@ of it as it can automatically (which in this case is just merge the `example`
 file, which had no differences in the `mybranch` branch), and say:
 
 ----------------
-       Trying really trivial in-index merge...
-       fatal: Merge requires file-level merging
-       Nope.
-       ...
        Auto-merging hello 
        CONFLICT (content): Merge conflict in hello 
        Automatic merge failed; fix up by hand
 ----------------
 
-which is way too verbose, but it basically tells you that it failed the
-really trivial merge ("Simple merge") and did an "Automatic merge"
-instead, but that too failed due to conflicts in `hello`.
+It tells you that it did an "Automatic merge", which
+failed due to conflicts in `hello`.
 
 Not to worry. It left the (trivial) conflict in `hello` in the same form you
 should already be well used to if you've ever used CVS, so let's just
index 4f424782ebbd90572793a86bce862f3b856f56e0..04475a92168feb98e0de1e386476ca702fb6c41b 100644 (file)
@@ -121,10 +121,6 @@ Undo a merge or pull::
 +
 ------------
 $ git pull                         <1>
-Trying really trivial in-index merge...
-fatal: Merge requires file-level merging
-Nope.
-...
 Auto-merging nitfol
 CONFLICT (content): Merge conflict in nitfol
 Automatic merge failed/prevented; fix up by hand