summaryrefslogtreecommitdiff
path: root/Documentation/git-diff-index.txt
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2011-05-26 22:33:15 -0400
committerJunio C Hamano <gitster@pobox.com>2011-05-26 22:15:39 -0700
commit62b42d348754231609e07912ac42da6b112008ef (patch)
tree951ae8a5851dfcc9cf3fae18c11433b411deb11c /Documentation/git-diff-index.txt
parent715e716a1b5bc1bc71715286e7a10b7e0c3188e8 (diff)
downloadgit-62b42d348754231609e07912ac42da6b112008ef.tar.gz
docs: fix some antique example output
These diff-index and diff-tree sample outputs date back to the first month of git's existence. The output format has changed slightly since then, so let's have it match the current output. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-diff-index.txt')
-rw-r--r--Documentation/git-diff-index.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-diff-index.txt b/Documentation/git-diff-index.txt
index 6d18486402..2ea22abca2 100644
--- a/Documentation/git-diff-index.txt
+++ b/Documentation/git-diff-index.txt
@@ -96,8 +96,8 @@ show that. So let's say that you have edited `kernel/sched.c`, but
have not actually done a 'git update-index' on it yet - there is no
"object" associated with the new state, and you get:
- torvalds@ppc970:~/v2.6/linux> git diff-index HEAD
- *100644->100664 blob 7476bb......->000000...... kernel/sched.c
+ torvalds@ppc970:~/v2.6/linux> git diff-index --abbrev HEAD
+ :100644 100664 7476bb... 000000... kernel/sched.c
i.e., it shows that the tree has changed, and that `kernel/sched.c` has is
not up-to-date and may contain new stuff. The all-zero sha1 means that to