Thread (3 messages) flat view 3 messages, 3 authors, 2016-06-15

Re: A few usability question about git diff --cached

From: Matthieu Moy <hidden>
Date: 2016-06-15 22:43:38

Johannes Schindelin [off-list ref] writes:
Hi,

On Thu, 4 Oct 2007, Junio C Hamano wrote:
quoted
 * --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".

So, to me (non-native speaker), "index" doesn't mean much, "cache" is
worse, it means something which isn't correct, and "staging area"
means the right thing (but is longer to type). For example, I
understand immediately when git-gui talks me about staging/unstaging
changes ;-).

-- 
Matthieu
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help