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

Re: [PATCH/RFC] gitk: refresh index before checking for local changes

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Apr 7, 2010, 02:57 UTC
Message-ID
<20100407025706.GA6528@progeny.tock>
In-Reply-To
<4BBBEC43.5000100@gmail.com>
A Large Angry SCM wrote:
[context: should gitk run ‘gitk update-index --refresh -q’ transparently?]
> NAK - gitk should not modify a repository and/or working dir unless
> _explicitly_ prompted to by the user.
>
> If you want a new _non-default_ option setting for gitk, that fine also.
I have some sympathy for this point of view.
Does the same principle apply to ‘git diff’?  If not, why not?

It should be possible to suppress files with no changes from the display without refreshing the index (or not to suppress them and to still refresh the index, nor that matter; the issues are orthogonal), but it would be nice to come up with a clear rationale first.

Jonathan
Previous: A Large Angry SCMNext: Junio C Hamano
Message 9 of 15 in “gitk pays too much attention to file timestamps”
  1. Alexander GladyshApr 6, 2010
  2. Markus HeidelbergApr 6, 2010
  3. Jonathan NiederApr 6, 2010
  4. Alexander GladyshApr 6, 2010
  5. gitk: refresh index before checking for local changesJonathan Nieder, Apr 7, 2010
  6. Alexander GladyshApr 7, 2010
  7. Jonathan NiederApr 7, 2010
  8. A Large Angry SCMApr 7, 2010
  9. Jonathan NiederApr 7, 2010
  10. Junio C HamanoApr 7, 2010
  11. A Large Angry SCMApr 7, 2010
  12. Avery PennarunApr 7, 2010
  13. Jon SeymourApr 7, 2010
  14. Avery PennarunApr 6, 2010
  15. Jonathan NiederApr 7, 2010

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.