git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/PATCH] update-index: Add a --refresh-only option to refresh specified files.

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 4, 2007, 18:34 UTC
Message-ID
<7vlkcrgnd1.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<87odhnk4cb.fsf@wine.dyndns.org>
Alexandre Julliard <julliard@winehq.org> writes:
Show 10 quoted lines
> This allows to quickly refresh a file that has been touched without
> having to stat all the files of the project.
>
> Signed-off-by: Alexandre Julliard <julliard@winehq.org>
> ---
>
> Does this look reasonable?  The refresh_index_path() function is a
> copy/paste of refresh_index(), I'm not sure all of it is really
> needed, but I don't claim to understand all the subtleties of the
> index management...
Makes me wonder why it is not like:
	$ git update-index --refresh Documentation/
That is:
 - why a new option?
 - why not a pathspec or glob, similar to what ls-files gets?
Previous: Alexandre JulliardNext: Alexandre Julliard
Message 2 of 3 in “update-index: Add a --refresh-only option to refresh specified files.”
  1. update-index: Add a --refresh-only option to refresh specified files.Alexandre Julliard, Aug 4, 2007
  2. Junio C HamanoAug 4, 2007
  3. Alexandre JulliardAug 4, 2007

Read the whole thread, see it on lore, or plain text.

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