Re: gitk pays too much attention to file timestamps
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Apr 7, 2010, 01:01 UTC
- Message-ID
- <20100407010109.GB11346@progeny.tock>
- In-Reply-To
- <u2r32541b131004061658r555f21dbgbe011960d9152d3c@mail.gmail.com>
Avery Pennarun wrote:
> 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.
Ah, yes, I am not thinking very well. Please forget what I said before.
v1.5.3-rc5~10 (git-diff: squelch "empty" diffs, 2007-08-03) has the answer for your question. I am not sure I agree with its conclusion.
v1.5.3~8 (git-diff: resurrect the traditional empty "diff --git" behaviour, 2007-08-31) tweaked the porcelain more by dropping the warning message and adding the diff.autorefreshindex variable.
What is missing is a --refresh-index option for diff-files and diff-index, to make it easy for porcelain, especially long-running porcelain like gitk.
Jonathan