From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 3/3] tutorial: add discussion of index file, object database
Date: Mon, 22 May 2006 17:27:31 +0200 [thread overview]
Message-ID: <e4sl90$l3b$1@sea.gmane.org> (raw)
In-Reply-To: 1148255528.61d5d241.2@fieldses.org
J. Bruce Fields wrote:
> +With the right arguments, git diff can also show us the difference
> +between the working directory and the last commit, or between the
> +index and the last commit:
> +
> +------------------------------------------------
> +$ git diff HEAD
[...]
> +$ git diff --cached
Junio C Hamano wrote:
> Also, ":<path>" to mean the
> entry in the index is often equivalent to "git diff --cached".
>
> IOW, these are obscure special purpose notation, and I do not
> think tutorial is a good place to cover them.
Hmm, wouldn't it be nice to have here :<path> mentioned as
alternative/extension to --cached, and <ref>:<path> including
HEAD:<path> as an extension of HEAD, and <path> as an extension
to not having arguments? By extension I mean adding path limiting
and some more advanced selection of things to diff.
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-05-22 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 23:53 (unknown) J. Bruce Fields
2006-05-21 23:53 ` (unknown) J. Bruce Fields
2006-05-21 23:53 ` (unknown) J. Bruce Fields
2006-05-22 0:35 ` totorial-2 (unknown) Junio C Hamano
2006-05-22 1:25 ` J. Bruce Fields
2006-05-22 15:27 ` Jakub Narebski [this message]
2006-05-22 8:23 ` [PATCH 2/3] tutorial: expanded discussion of commit history Jakub Narebski
2006-05-22 8:45 ` Junio C Hamano
2006-05-22 9:01 ` Jakub Narebski
2006-05-22 14:18 ` J. Bruce Fields
2006-05-21 23:55 ` your mail J. Bruce Fields
2006-05-22 0:16 ` Junio C Hamano
2006-05-22 1:33 ` J. Bruce Fields
2006-05-22 10:09 ` [PATCH] git help: remove whatchanged from list of common commands Martin Waitz
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='e4sl90$l3b$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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.