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

From: Alexandre Julliard <julliard@winehq.org>
Date: Aug 1, 2007, 19:02 UTC
Message-ID: <87vebzkrid.fsf@wine.dyndns.org>
In-Reply-To: <7v4pjj5fp6.fsf@assigned-by-dhcp.cox.net>

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

Show 5 quoted lines

> Yes.  Very much so, intentionally, from very early days of git.
> This serves as a reminder to the user that he started editing
> but changed his mind to end up with the same contents as the
> original, until the next "update-index --refresh" (which is
> internally invoked from "status").

It would be nice to have a way to refresh a single file though. For instance in vc-git.el the workfile-unchanged-p function currently has to rehash the file every time to see if it really changed, because we can't afford to refresh the whole project at that point.

-- 
Alexandre Julliard
julliard@winehq.org

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