SYNOPSIS
--------
-- 'git-diff' [ --diff-options ] <commit>{0,2} [--] [<path>...]
++ 'git-diff' [<common diff options>] <commit>{0,2} [--] [<path>...]
DESCRIPTION
-----------
further add to the index but you still haven't. You can
stage these changes by using gitlink:git-add[1].
+ If exactly two paths are given, and at least one is untracked,
+ compare the two files / directories. This behavior can be
+ forced by --no-index.
+
'git-diff' [--options] --cached [<commit>] [--] [<path>...]::
This form is to view the changes you staged for the next
You are reading the documentation for the latest version of git.
Documentation for older releases are available here:
+* link:v1.5.0.3/git.html[documentation for release 1.5.0.3]
+
+* link:v1.5.0.3/RelNotes-1.5.0.3.txt[release notes for 1.5.0.3]
+
+* link:v1.5.0.2/RelNotes-1.5.0.2.txt[release notes for 1.5.0.2]
+
+* link:v1.5.0.1/RelNotes-1.5.0.1.txt[release notes for 1.5.0.1]
+
+* link:v1.5.0/RelNotes-1.5.0.txt[release notes for 1.5.0]
+
* link:v1.4.4.4/git.html[documentation for release 1.4.4.4]
* link:v1.3.3/git.html[documentation for release 1.3.3]
operate on a <tree> object but automatically dereferences
<commit> and <tag> objects that point at a <tree>.
++ <commit-ish>::
++ Indicates a commit or tag object name. A
++ command that takes a <commit-ish> argument ultimately wants to
++ operate on a <commit> object but automatically dereferences
++ <tag> objects that point at a <commit>.
++
<type>::
Indicates that an object type is required.
Currently one of: `blob`, `tree`, `commit`, or `tag`.