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

From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Aug 2, 2007, 14:49 UTC
Message-ID: <vpq7ioeyosh.fsf@bauges.imag.fr>
In-Reply-To: <Pine.LNX.4.64.0708021537490.14781@racer.site>

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

>> 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

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.