From a8adb1ec550d7d7a66cd4d362cfbd01795d71f43 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Mon, 10 Apr 2006 23:46:16 +0000 Subject: [PATCH] Autogenerated HTML docs for v1.3.0-rc3-g5910 --- git-diff-tree.html | 32 ++++++++++++++++++++++---------- git-diff-tree.txt | 25 ++++++++++++++++--------- 2 files changed, 38 insertions(+), 19 deletions(-) diff --git a/git-diff-tree.html b/git-diff-tree.html index 508d336c..f616fd6e 100644 --- a/git-diff-tree.html +++ b/git-diff-tree.html @@ -531,7 +531,8 @@ separated with a single space are given.

By default, "git-diff-tree --stdin" does not show differences for merge commits. With this flag, it shows - differences to that commit from all of its parents. + differences to that commit from all of its parents. See + also -c.

@@ -574,22 +575,33 @@ separated with a single space are given.

--c,--cc +-c

- These flags change the way a merge commit is displayed + This flag changes the way a merge commit is displayed (which means it is useful only when the command is given one <tree-ish>, or --stdin). It shows the differences - from each of the parents to the merge result - simultaneously, instead of showing pairwise diff between - a parent and the result one at a time, which -m option - output does. --cc further compresses the output by - omiting hunks that show differences from only one + from each of the parents to the merge result simultaneously + instead of showing pairwise diff between a parent and the + result one at a time (which is what the -m option does). + Furthermore, it lists only files which were modified + from all parents. +

+
+
+-cc +
+
+

+ This flag changes the way a merge commit patch is displayed, + in a similar way to the -c option. It implies the -c + and -p options and further compresses the patch output + by omitting hunks that show differences from only one parent, or show the same change from all but one parent for an Octopus merge. When this optimization makes all hunks disappear, the commit itself and the commit log - message is not shown, just like any other "empty diff" cases. + message is not shown, just like in any other "empty diff" case.

@@ -964,7 +976,7 @@ two unresolved merge parents with the working tree file diff --git a/git-diff-tree.txt b/git-diff-tree.txt index 9153e4cf..21691698 100644 --- a/git-diff-tree.txt +++ b/git-diff-tree.txt @@ -60,7 +60,8 @@ separated with a single space are given. -m:: By default, "git-diff-tree --stdin" does not show differences for merge commits. With this flag, it shows - differences to that commit from all of its parents. + differences to that commit from all of its parents. See + also '-c'. -s:: By default, "git-diff-tree --stdin" shows differences, @@ -81,19 +82,25 @@ separated with a single space are given. git-diff-tree outputs a line with the commit ID when applicable. This flag suppressed the commit ID output. --c,--cc:: - These flags change the way a merge commit is displayed +-c:: + This flag changes the way a merge commit is displayed (which means it is useful only when the command is given one , or '--stdin'). It shows the differences - from each of the parents to the merge result - simultaneously, instead of showing pairwise diff between - a parent and the result one at a time, which '-m' option - output does. '--cc' further compresses the output by - omiting hunks that show differences from only one + from each of the parents to the merge result simultaneously + instead of showing pairwise diff between a parent and the + result one at a time (which is what the '-m' option does). + Furthermore, it lists only files which were modified + from all parents. + +-cc:: + This flag changes the way a merge commit patch is displayed, + in a similar way to the '-c' option. It implies the '-c' + and '-p' options and further compresses the patch output + by omitting hunks that show differences from only one parent, or show the same change from all but one parent for an Octopus merge. When this optimization makes all hunks disappear, the commit itself and the commit log - message is not shown, just like any other "empty diff" cases. + message is not shown, just like in any other "empty diff" case. --always:: Show the commit itself and the commit log message even -- 2.11.0