summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2010-10-11 16:04:08 (GMT)
committerJunio C Hamano <gitster@pobox.com>2010-10-14 02:10:56 (GMT)
commited84e6d511f9e754d6331c63468bf7421b1e0894 (patch)
tree93737211be7b164d0243cfd00dc98edcd8590474
parent9d83e3827fc1031bbcafb0d26128e95dda306aed (diff)
downloadgit-ed84e6d511f9e754d6331c63468bf7421b1e0894.zip
git-ed84e6d511f9e754d6331c63468bf7421b1e0894.tar.gz
git-ed84e6d511f9e754d6331c63468bf7421b1e0894.tar.bz2
Documentation: diff can compare blobs
Meanwhile, there is no plumbing command to compare two blobs. Strange. Reported-by: Yann Dirson <dirson@bertin.fr> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-diff.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/git-diff.txt b/Documentation/git-diff.txt
index 481a33c..db2c6c2 100644
--- a/Documentation/git-diff.txt
+++ b/Documentation/git-diff.txt
@@ -64,8 +64,9 @@ forced by --no-index.
Just in case if you are doing something exotic, it should be
noted that all of the <commit> in the above description, except
-for the last two forms that use ".." notations, can be any
-<tree-ish>.
+in the last two forms that use ".." notations, can be any
+<tree>. The third form ('git diff <commit> <commit>') can also
+be used to compare two <blob> objects.
For a more complete list of ways to spell <commit>, see
"SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].