From: Andreas Ericsson <ae@op5.se>
To: git@vger.kernel.org
Subject: Re: [PATCH] Change 'cache' to 'index' in the docs
Date: Fri, 11 Nov 2005 12:49:58 +0100 [thread overview]
Message-ID: <43748566.2070204@op5.se> (raw)
In-Reply-To: <7voe4svufi.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Lukas Sandstr^[.A^[Nvm <lukass@etek.chalmers.se> writes:
>
>
>>git-update-index.txt says:
>>"Modifies the index or directory cache."
>>
>>I thought the index was the directory cache.
>>Is git-update-index.txt badly worded or is there something
>>I'm missing?
>
>
> Nothing. Just 'cache' is so ingrained to the brain of some/many
> of us that we let it go unnoticed, with an excuse that somewhere
> we say "index aka cache".
>
This had me puzzled for quite some time. Some notice to the tutorial
about what's meant when it says "tree-ish" or "commit-ish" would be nice
(I still haven't been able to figure it out).
The wording in git-diff-index.txt isn't exactly stellar either. The
git(7) man-page mentions that it's nice to read git-diff-index before
doing anything else, but it was just yesterday before I figured out that
it can be used to produce a diff between an updated index and the
checked out working tree (which has led me to some fairly obscure
juggling with patches and source-files to remember just what the hell it
was I changed).
Oh well. Perhaps I checked in all the wrong places.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-11-11 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 1:12 [PATCH] Change 'cache' to 'index' in the docs Lukas Sandström
2005-11-11 1:34 ` Junio C Hamano
2005-11-11 11:49 ` Andreas Ericsson [this message]
2005-11-11 14:15 ` Johannes Schindelin
2005-11-11 14:34 ` Andreas Ericsson
2005-11-11 15:35 ` Johannes Schindelin
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=43748566.2070204@op5.se \
--to=ae@op5.se \
--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.