Jonathan,
thank you for the explanation!
<...>
> 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 *think* that 1.6.x didn't have this issue. (Sorry, can't check now.)
> 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
> [diff]
> autoRefreshIndex = false
> in their configuration file, so the rest of us don’t have to suffer
> from the confusing behavior.
> As some kind of evil compromise, it might be worth teaching gitk
> to check the same configuration and run update-index --refresh in
> getcommits{} if and only if it is unset or set to true.
> Thoughts?
That's fine as far as I'm concerned.
The current behaviour is really annoying.
If I want something fast, I do not use GUI tools. Gitk starts up
rather slowly on my box anyway.
Alexander.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html