Re: git-diff on touched files: bug or feature?

From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Aug 2, 2007, 12:26 UTC
Message-ID: <vpqir7y15sr.fsf@bauges.imag.fr>
In-Reply-To: <Pine.LNX.4.64.0708021315510.14781@racer.site>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 7 quoted lines

>> I fully agree that git should be optimized for the common case. But
>> even for the common case, I also find the feature strange. You didn't
>> answer that part of my message, but I still fail to see a rationale
>> for making "git-diff; git-status" different from "git-status; git-diff".
>
> For performance reasons, git always compares the files' stat information 
> with that stored in the index.

I know that, but how does it answer the part of my message that you are citing?

> So when you do "git diff" and it tells you all those diff lines, while no 
> file was really changed, it tells you "get your act together!  You just 
> _willfully_ slowed down git's performance".

The question remains: why should someone running git-diff get this, and someone running git-status not get this?

(I mean, from the user point of view, not the implementation point of view)

-- 
Matthieu