aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2006-02-02 11:28:38 -0800
committerJunio C Hamano <junkio@cox.net>2006-02-02 11:28:38 -0800
commit985cb9cc5851ae2f65acf74a8db5077b69cc2a9b (patch)
tree9493eb2b4a2da718c49777cdad6cffa5748ea6db
parent823bcd6edc7f7330714486b228b052953c2f4229 (diff)
downloadgit-985cb9cc5851ae2f65acf74a8db5077b69cc2a9b.tar.gz
git-985cb9cc5851ae2f65acf74a8db5077b69cc2a9b.tar.xz
Documentation: git-diff-tree --cc also omits empty commits
A misguided attempt to show logs at all time was inserted only to the documentation of this flag. Worse yet, it was not even implemented, causing more confusion. Drop it. We might want to have an option to show --pretty even when there is no diff output, but that is applicable to all forms of diff, not just --cc. Signed-off-by: Junio C Hamano <junkio@cox.net>
-rw-r--r--Documentation/git-diff-tree.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-diff-tree.txt b/Documentation/git-diff-tree.txt
index dd46d4f05..674ee614c 100644
--- a/Documentation/git-diff-tree.txt
+++ b/Documentation/git-diff-tree.txt
@@ -93,7 +93,7 @@ separated with a single space are given.
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, unless '-m' is specified.
+ message is not shown, just like any other "empty diff" cases.
Limiting Output