From: Eric Raible <raible@nextest.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>, Lasse Makholm <lasse.makholm@gmail.com>
Subject: Re: [PATCH 2/2] update $GIT_INDEX_FILE when there are racily clean entries
Date: Mon, 21 Mar 2011 17:26:54 -0700 [thread overview]
Message-ID: <4D87ECCE.4000300@nextest.com> (raw)
In-Reply-To: <7voc54qtmf.fsf@alter.siamese.dyndns.org>
On 11:59 AM, Junio C Hamano wrote:
> Traditional "opportunistic index update" done by read-only "diff" and
> "status" was about updating cached lstat(2) information in the index for
> the next round. We missed another obvious optimization opportunity to
> when there are racily clean entries that will ceas to be racily clean
> by updating $GIT_INDEX_FILE.
s/ceas/cease/
next prev parent reply other threads:[~2011-03-22 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 12:40 git status reads too many files Lasse Makholm
2011-03-21 16:41 ` Junio C Hamano
2011-03-21 17:16 ` [PATCH 1/2] diff/status: refactor opportunistic index update Junio C Hamano
2011-03-21 18:46 ` Piotr Krukowiecki
2011-03-21 19:39 ` Junio C Hamano
2011-03-21 17:18 ` [PATCH 2/2] update $GIT_INDEX_FILE when there are racily clean entries Junio C Hamano
2011-03-21 21:23 ` Lasse Makholm
2011-03-22 0:26 ` Eric Raible [this message]
2011-03-21 20:39 ` git status reads too many files Lasse Makholm
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=4D87ECCE.4000300@nextest.com \
--to=raible@nextest.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=lasse.makholm@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.