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

From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Aug 2, 2007, 12:08 UTC
Message-ID: <vpqzm1a2l72.fsf@bauges.imag.fr>
In-Reply-To: <7v1wemxnkk.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <gitster@pobox.com> writes:

> Quite honestly, a script that indiscriminately touches everybody
> but only modifies a few is simply broken.  Think about "make".
> "git diff" reporting many cache-dirty files is simply reminding
> you the brokenness of such a script.

I wouldn't call this "broken", but clearly suboptimal, yes. But for an occasionnal one-liner (perl -pi -e ... or so), I lose less time recompiling extra-files than I would writting a cleaner script. "make" has no way to detect the absence of modification, while git has.

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