From: "Jonathan del Strother" <maillist@steelskies.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] don't mention index refreshing side effect in git-status docs
Date: Sun, 9 Dec 2007 16:16:13 +0000 [thread overview]
Message-ID: <57518fd10712090816pa43cf97mbc1b8f5fbe81c66f@mail.gmail.com> (raw)
In-Reply-To: <20071209082133.GA2257@coredump.intra.peff.net>
On Dec 9, 2007 8:21 AM, Jeff King <peff@peff.net> wrote:
> 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" ?
next prev parent reply other threads:[~2007-12-09 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 8:21 [PATCH] don't mention index refreshing side effect in git-status docs Jeff King
2007-12-09 8:33 ` Junio C Hamano
2007-12-09 8:42 ` Jeff King
2007-12-09 16:16 ` Jonathan del Strother [this message]
2007-12-09 18:15 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57518fd10712090816pa43cf97mbc1b8f5fbe81c66f@mail.gmail.com \
--to=maillist@steelskies.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).