From: Junio C Hamano <gitster@pobox.com>
To: David Turner <dturner@twopensource.com>
Cc: git@vger.kernel.org, Brian Degenhardt <bmd@bmdhacks.com>
Subject: Re: [PATCH] cache-tree: populate cache-tree on successful merge
Date: Tue, 28 Jul 2015 13:04:39 -0700 [thread overview]
Message-ID: <xmqq1tfsdp60.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqq6154dpkt.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Tue, 28 Jul 2015 12:55:46 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> David Turner <dturner@twopensource.com> writes:
>
>> The work done to produce the cache-tree is work that the commit would
>> otherwise have to do. So we're spending extra time in one place to
>> eliminate that work in a different place.
>
> Good point. Thanks.
Hmm, I forgot about another codepath. What about operations that
are purely done to pouplate the index, without necessarily creating
a tree out of the index?
The most worrisome is "git checkout $branch" (two-tree merge).
next prev parent reply other threads:[~2015-07-28 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 19:30 [PATCH] cache-tree: populate cache-tree on successful merge David Turner
2015-07-28 19:50 ` Junio C Hamano
2015-07-28 19:54 ` David Turner
2015-07-28 19:55 ` Junio C Hamano
2015-07-28 20:04 ` Junio C Hamano [this message]
2015-07-28 20:28 ` David Turner
2015-07-28 20:58 ` Junio C Hamano
2015-07-28 20:47 ` Junio C Hamano
2015-07-28 21:18 ` David Turner
2015-07-28 21:38 ` 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=xmqq1tfsdp60.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=bmd@bmdhacks.com \
--cc=dturner@twopensource.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 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.