From: Junio C Hamano <gitster@pobox.com>
To: Karl Chen <quarl@cs.berkeley.edu>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: [PATCH] Support diff.autorefreshindex=true in `git-diff --quiet'
Date: Tue, 02 Sep 2008 10:47:47 -0700 [thread overview]
Message-ID: <7v4p4ymocc.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <quack.20080902T1039.lthabeqmopo_-_@roar.cs.berkeley.edu> (Karl Chen's message of "Tue, 02 Sep 2008 10:39:47 -0700")
Karl Chen <quarl@cs.berkeley.edu> writes:
> If anyone actually used the old behavior of ignoring
> diff.autorefreshindex (as an optimization, because the script ran
> update-index --refresh outside a loop), there could be a --quick
> option, or they could use git-diff-files.
No, that actually is a wrong attitude.
If somebody's depending on the behaviour, it is this new behaviour of
doing everything asked without shortcut that needs to become a new
option.
What tempted me to suggest the simpler and potentially slower approach was
my hunch that no sane people depended on the old behaviour.
next prev parent reply other threads:[~2008-09-02 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 8:29 [PATCH] Support diff.autorefreshindex=true in `git-diff --quiet' Karl Chen
2008-09-01 10:31 ` Junio C Hamano
2008-09-01 10:50 ` Karl Chen
2008-09-02 6:20 ` Re* " Junio C Hamano
2008-09-02 17:39 ` Karl Chen
2008-09-02 17:47 ` Junio C Hamano [this message]
2008-09-02 17:59 ` Karl Chen
2008-09-02 20:19 ` 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=7v4p4ymocc.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=quarl@cs.berkeley.edu \
/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).