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

Re: gitk pays too much attention to file timestamps

From
Avery Pennarun <apenwarr@gmail.com>
Date
Apr 6, 2010, 23:58 UTC
Message-ID
<u2r32541b131004061658r555f21dbgbe011960d9152d3c@mail.gmail.com>
In-Reply-To
<20100406233601.GA27533@progeny.tock>
On Tue, Apr 6, 2010 at 7:36 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 8 quoted lines
> gitk is something of a passive observer of the index, which is
> actually something I like about it.  This keeps it relatively fast
> and can be useful when trying to understand other commands.
>
> I am not sure how other people use gitk, though.  Maybe this would
> be worth changing.  For a reference point, another command in a
> very similar situation is ‘git diff’: people who want the speedup
> from avoiding refreshing the index with that command use

Isn't it kind of weird, then, that it bothers to check the stat information at all? I'm not sure why I'd want to know accurately whether or not my file matches the index, but then have gitk fail to tell me about *what* doesn't match. If it has to check the stat() information anyway, isn't it already being slow?

Avery
Previous: Jon SeymourNext: Jonathan Nieder
Message 14 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.