From: "J. Bruce Fields" <bfields@fieldses.org>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>,
Miklos Vajna <vmiklos@frugalware.org>,
Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: A few usability question about git diff --cached
Date: Thu, 4 Oct 2007 11:51:47 -0400 [thread overview]
Message-ID: <20071004155147.GA17487@fieldses.org> (raw)
In-Reply-To: <vpqtzp7ndn3.fsf@bauges.imag.fr>
On Thu, Oct 04, 2007 at 04:44:00PM +0200, Matthieu Moy wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > Hi,
> >
> > On Thu, 4 Oct 2007, Junio C Hamano wrote:
> >
> >> * --cached means work only on index and ignore work tree.
> >
> > I guess I could live with "--staged" as a synonym for "--cached" (and
> > maybe deprecating "--cached").
>
> It makes more sense to me.
>
> For me, a "cache" is a fast-access copy of something, that I can
> rebuild at any time. Cache should be only a matter of performance, if
> the "cache" for an application changes its functionality, it means the
> cache has been too optimistic. Git's index is not that, "git add"
> means "add this to the index", which itself means "put that in the
> list of things to commit", and not "get a copy of that to work faster
> with it".
Yes, the index differs from the work tree or HEAD temporarily, but most
of it's life it's just a fast-access copy of something that you can
rebuild at any time.
So it's partly a "cache", partly a "staging area", and "index" is as
good a term for it as any.
--b.
next prev parent reply other threads:[~2007-10-04 15:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 12:27 A few usability question about git diff --cached Paolo Ciarrocchi
2007-10-04 12:54 ` Wincent Colaiuta
2007-10-05 5:59 ` Miles Bader
2007-10-05 10:27 ` Wincent Colaiuta
2007-10-05 10:41 ` Miles Bader
2007-10-04 12:56 ` Miklos Vajna
2007-10-04 13:10 ` Paolo Ciarrocchi
2007-10-04 13:14 ` Junio C Hamano
2007-10-04 13:39 ` Paolo Ciarrocchi
2007-10-04 14:09 ` Wincent Colaiuta
2007-10-04 14:34 ` Johannes Schindelin
2007-10-04 14:40 ` Junio C Hamano
2007-10-04 14:47 ` David Kastrup
2007-10-04 14:44 ` Matthieu Moy
2007-10-04 15:51 ` J. Bruce Fields [this message]
2007-10-04 16:02 ` Matthieu Moy
2007-10-04 16:19 ` J. Bruce Fields
2007-10-05 6:40 ` Matthieu Moy
2007-10-05 5:22 ` David Tweed
2007-10-04 15:49 ` Wincent Colaiuta
-- strict thread matches above, loose matches on Subject: below --
2021-08-14 19:31 Court Rankin
2023-01-12 11:54 Mohammed Al-Mahmeed
2024-07-02 14:13 Kenneth Porter
2024-07-02 14:13 Kenneth Porter
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=20071004155147.GA17487@fieldses.org \
--to=bfields@fieldses.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paolo.ciarrocchi@gmail.com \
--cc=vmiklos@frugalware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).