From: Linus Torvalds <torvalds@osdl.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: [RFC] git-add update with all-0 object
Date: Thu, 30 Nov 2006 23:10:36 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0611302306120.3695@woody.osdl.org> (raw)
In-Reply-To: <20061201045727.GA22622@thunk.org>
On Thu, 30 Nov 2006, Theodore Tso wrote:
>
> By the way, after thinking about this for a while, part of the problem
> is that the name "index" really sucks.
Hey, it was originally called "cache".
I don't care _what_ it's called, I just want people knowing about it,
because hiding it will just cripple git (ie at the very least, when you
hit a merge conflict, you really do want to to understand it if you ever
want to go the the "next level").
If people are more comfortable just calling it the "staging area", and
talking about it in those terms, I'll be happy.
> Put another way, the reason why I think people are liking the whole
> "git add" and "git rm" suggestion is that it's a nice middle ground
> between the "hide the index" and the "shove the index in the user's
> face" approaches. It's not that we are hiding the fact that there is
> this thing with the horribly chosen name "index", but instead we talk
> about this concept of a staging area and we don't dwell on things like
> the fact that it is a binary file which stores an efficient
> representation of a virtual directory.... blah blah blah.
Yes.
And even "git diff" isn't really a problem once you understand the staging
area. If people feel worried, let them use "git diff HEAD". You won't need
to use git for _that_ long until you realize that since the staging area
is going to match the HEAD under normal circumstances (and when it
doesn't, you actually tend to prefer to get the diff against the staging
area _anyway_), you'll find people just starting to use "git diff" and not
worry about it.
next prev parent reply other threads:[~2006-12-01 7:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 22:08 [RFC] git-add update with all-0 object Daniel Barkalow
2006-11-30 22:32 ` Johannes Schindelin
2006-11-30 22:34 ` Nicolas Pitre
2006-11-30 22:41 ` Jakub Narebski
2006-11-30 22:49 ` Nicolas Pitre
2006-11-30 22:46 ` Linus Torvalds
2006-12-01 0:12 ` Daniel Barkalow
2006-12-01 4:57 ` Theodore Tso
2006-12-01 6:20 ` Junio C Hamano
2006-12-02 8:55 ` Jakub Narebski
2006-12-01 7:10 ` Linus Torvalds [this message]
2006-12-01 8:10 ` Daniel Barkalow
2006-12-01 9:37 ` Andy Parkins
2006-12-02 8:35 ` Jakub Narebski
2006-12-02 8:26 ` Jakub Narebski
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=Pine.LNX.4.64.0611302306120.3695@woody.osdl.org \
--to=torvalds@osdl.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=tytso@mit.edu \
/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).