Ramkumar Ramachandra wrote: > In DESCRIPTION, the '<commit>..<commit>' form refers to "the previous > form", namely the '<commit> <commit>' form. However, bd52900 Good catch. [...] > --- a/Documentation/git-diff.txt > +++ b/Documentation/git-diff.txt > @@ -11,8 +11,8 @@ SYNOPSIS > [verse] > '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] <commit> <commit> [--] [<path>...] > 'git diff' [options] [--no-index] [--] <path> <path> For the sake of exposition I think it makes more sense to put <commit> <commit> *before* <blob> <blob>, since the former is used more often. Thanks, Jonathan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html