From: Jakub Narebski <jnareb@gmail.com>
To: Yann Dirson <dirson@bertin.fr>
Cc: "Santi Béjar" <santi@agolina.net>, git@vger.kernel.org
Subject: Re: Undocumented git-diff syntax
Date: Mon, 11 Oct 2010 09:57:48 -0700 (PDT) [thread overview]
Message-ID: <m3wrpoekha.fsf@localhost.localdomain> (raw)
In-Reply-To: <20101011161721.35940919@chalon.bertin.fr>
Yann Dirson <dirson@bertin.fr> writes:
> That said, this two-path construct would surely deserve its own
> synopsis.
Something like this? Just kidding...
SYNOPSIS
--------
+[verse]
'git diff' [<common diff options>] <commit>{0,2} [--] [<path>...]
+'git diff' [<common diff options>] <tree-ish> <tree-ish> [--] [<path>...]
+'git diff' [<common diff options>] <blob-or-path> <blob-or-path>
Possibly that <tree-ish> can be also a <directory> (on filesystem).
You can e.g. use
git diff HEAD:git-gui/ 00e9de7^^
^^^^^^^^^^^^^ ~~~~~~~~~
\-- tree \-- commit (in subtree-merged history)
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2010-10-11 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 13:03 Undocumented git-diff syntax Yann Dirson
2010-10-11 13:59 ` Santi Béjar
2010-10-11 14:17 ` Yann Dirson
2010-10-11 14:52 ` Santi Béjar
2010-10-11 16:02 ` [PATCH 0/4] " Jonathan Nieder
2010-10-11 16:03 ` [PATCH 1/5] Documentation: gitrevisions is in section 7 Jonathan Nieder
2010-10-11 20:49 ` Sverre Rabbelier
2010-10-11 16:04 ` [PATCH 2/4] Documentation: diff can compare blobs Jonathan Nieder
2010-10-11 16:05 ` [PATCH 3/4] Documentation: expand 'git diff' SEE ALSO section Jonathan Nieder
2010-10-11 16:06 ` [PATCH 4/4] Documentation: update "git diff --no-index" description Jonathan Nieder
2010-10-11 16:07 ` [RFC/PATCH 5/4] Documentation: flesh out diff --no-index description Jonathan Nieder
2010-10-13 22:40 ` Junio C Hamano
2010-10-11 18:52 ` [PATCH 0/4] Re: Undocumented git-diff syntax Yann Dirson
2010-10-11 20:56 ` Sverre Rabbelier
2010-10-11 16:57 ` Jakub Narebski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wrpoekha.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=dirson@bertin.fr \
--cc=git@vger.kernel.org \
--cc=santi@agolina.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.