alllexx88
commented
8 years ago git manuals are in git-nampages package:
DiskStation> ipkg install git-manpages git
Installing git-manpages (2.6.5-1) to /opt/...
Downloading http://ipkg.nslu2-linux.org/optware-ng/buildroot-i686/git-manpages_2.6.5-1_i686.ipk
Upgrading git on /opt/ from 2.6.3-1 to 2.6.5-1...
Downloading http://ipkg.nslu2-linux.org/optware-ng/buildroot-i686/git_2.6.5-1_i686.ipk
Configuring git
Configuring git-manpages
Successfully terminated.
DiskStation> git diff --help
GIT-DIFF(1) Git Manual GIT-DIFF(1)
NAME
git-diff - Show changes between commits, commit and working tree, etc
SYNOPSIS
git diff [options] [<commit>] [--] [<path>...]
git diff [options] --cached [<commit>] [--] [<path>...]
git diff [options] <commit> <commit> [--] [<path>...]
git diff [options] <blob> <blob>
git diff [options] [--no-index] [--] <path> <path>
DESCRIPTION
Show changes between the working tree and the index or a tree, changes between the index and a tree, changes between two trees, changes between two blob objects,
or changes between two files on disk.
git diff [--options] [--] [<path>...]
This form is to view the changes you made relative to the index (staging area for the next commit). In other words, the differences are what you could tell Git
to further add to the index but you still haven't. You can stage these changes by using git-add(1).
git diff --no-index [--options] [--] [<path>...]
This form is to compare the given two paths on the filesystem. You can omit the --no-index option when running the command in a working tree controlled by Git
and at least one of the paths points outside the working tree, or when running the command outside a working tree controlled by Git.
git diff [--options] --cached [<commit>] [--] [<path>...]
This form is to view the changes you staged for the next commit relative to the named <commit>. Typically you would want comparison with the latest commit, so
if you do not give <commit>, it defaults to HEAD. If HEAD does not exist (e.g. unborn branches) and <commit> is not given, it shows all staged changes.
--staged is a synonym of --cached.
git diff [--options] <commit> [--] [<path>...]
This form is to view the changes you have in your working tree relative to the named <commit>. You can use HEAD to compare it with the latest commit, or a
branch name to compare with the tip of a different branch.
git diff [--options] <commit> <commit> [--] [<path>...]
This is to view the changes between two arbitrary <commit>.
git diff [--options] <commit>..<commit> [--] [<path>...]
This is synonymous to the previous form. If <commit> on one side is omitted, it will have the same effect as using HEAD instead.
git diff [--options] <commit>...<commit> [--] [<path>...]
This form is to view the changes on the branch containing and up to the second <commit>, starting at a common ancestor of both <commit>. "git diff A...B" is
equivalent to "git diff $(git-merge-base A B) B". You can omit any one of <commit>, which has the same effect as using HEAD instead.
Just in case if you are doing something exotic, it should be noted that all of the <commit> in the above description, except in the last two forms that use ".."
notations, can be any <tree>.
...
Hi
git is missing manuals
$ git diff --help No manual entry for git-diff
Regards