Re: [PATCH] don't mention index refreshing side effect in git-status docs

From: Jonathan del Strother <maillist@steelskies.com>
Date: Dec 9, 2007, 16:16 UTC
Message-ID: <57518fd10712090816pa43cf97mbc1b8f5fbe81c66f@mail.gmail.com>
In-Reply-To: <20071209082133.GA2257@coredump.intra.peff.net>

On Dec 9, 2007 8:21 AM, Jeff King <peff@peff.net> wrote:

Show 12 quoted lines

> The tip about speeding up subsequent operations is now
> obsolete; since aecbf914, git-diff now squelches empty diffs
> and performs an automatic refresh.
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> This is on top of my other patches to the git-status docs.
>
> I don't see any reason to mention this side effect at all. Those who
> know enough to set diff.autorefreshindex presumably know what they are
> doing, and the removed paragraph is a bit confusing to those who don't.
>

... I wasn't aware the index needed refreshing. This might be totally unrelated to the present conversation, but the GIT-VERSION-GEN script occasionally gives me spurious 'dirty' results (eg when a file timestamp changes despite the content having changed). Should it perhaps be running "git update-index --refresh" before it runs "git diff-index --name-only HEAD" ?