Johannes Schindelin [off-list ref] writes:
quoted
The question remains: why should someone running git-diff get this,
and someone running git-status not get this?
Because git-status is an index-updating operation. That's why.
That sounds like "it is this way because it is not the other way
around".
So, yes, git-status updates the index because it's an index-updating
operation, while git-diff does not update the index because it's a
non-index-updating operation.
Then, I'll rephrase my sentence as "*why* is git-status an
index-updating operation while git-diff is not". But you'll probably
find another way to avoid answering.
--
Matthieu
Hi,
On Thu, 2 Aug 2007, Matthieu Moy wrote:
Johannes Schindelin [off-list ref] writes:
quoted
quoted
The question remains: why should someone running git-diff get this,
and someone running git-status not get this?
Because git-status is an index-updating operation. That's why.
That sounds like "it is this way because it is not the other way
around".
So, yes, git-status updates the index because it's an index-updating
operation, while git-diff does not update the index because it's a
non-index-updating operation.
Then, I'll rephrase my sentence as "*why* is git-status an
index-updating operation while git-diff is not". But you'll probably
find another way to avoid answering.
Yes. I do. The issue whether or not git status should be a read-only
operation has been discussed -- in _length_ -- here:
http://thread.gmane.org/gmane.comp.version-control.git/40205/focus=40339
Ciao,
Dscho