Re: A few usability question about git diff --cached
- From
- Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
- Date
- Oct 4, 2007, 13:10 UTC
- Message-ID
- <4d8e3fd30710040610m49521fb7ld8f95043c945bf94@mail.gmail.com>
- In-Reply-To
- <20071004125641.GE15339@genesis.frugalware.org>
On 10/4/07, Miklos Vajna <vmiklos@frugalware.org> wrote:
Show 8 quoted lines
> On Thu, Oct 04, 2007 at 02:27:41PM +0200, Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote: > > Why do we have the option "--cached" and not "--index"? > > according to glossary.txt, 'cache' is an obsolete for 'index'. probably > this is the reason > > probably cache.h will be never renamed to index.h, i don't know if diff > --cached will be ever renamed to diff --index
Believe me, for a GIT newbie git --cached is confusing.
That user started reading "A tutorial introduction to git (for version 1.5.1 or newer)", after a cuple of minutes of reading he reached "Making changes" saw:
" You are now ready to commit. You can see what is about to be committed using git-diff(1) with the —cached option:
$ git diff --cached "
$ git diff --index sound a lof more consistent with the general documentation.
Regards,
-- Paolo http://paolo.ciarrocchi.googlepages.com/ http://ubuntista.blogspot.com