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

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

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

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

"J. Bruce Fields" [off-list ref] writes:
Yes, the index differs from the work tree or HEAD temporarily, 
Temporarily, yes, but the _point_ of having it is to have it differ
from HEAD (otherwise, you can't create a new revision), and from the
tree (otherwise, index-related commands are useless).

The stat-information, and sha1sum are actually a cache, but they don't
have to be user-visible, except for speed. "diff --cached" has nothing
to do with the stat information for the user.

-- 
Matthieu

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

From: J. Bruce Fields <hidden>
Date: 2016-06-15 22:43:38

On Thu, Oct 04, 2007 at 06:02:21PM +0200, Matthieu Moy wrote:
"J. Bruce Fields" [off-list ref] writes:
quoted
Yes, the index differs from the work tree or HEAD temporarily, 
Temporarily, yes, but the _point_ of having it is to have it differ
from HEAD (otherwise, you can't create a new revision), and from the
tree (otherwise, index-related commands are useless).
Getting a nearly-instantaneous "git diff" would be sufficiently
important to justify its existance on its own, so I think you're
overstating the case.
The stat-information, and sha1sum are actually a cache, but they don't
have to be user-visible, except for speed.
That's a big exception.--b.
"diff --cached" has nothing to do with the stat information for the
user.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help