Thread (12 messages) flat view 12 messages, 6 authors, 2016-06-15

Re: gitk pays too much attention to file timestamps

From: Avery Pennarun <hidden>
Date: 2016-06-15 22:48:34

On Tue, Apr 6, 2010 at 7:36 PM, Jonathan Nieder [off-list ref] wrote:
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help