From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: David Turner <dturner@twopensource.com>,
Git Mailing List <git@vger.kernel.org>,
David Turner <dturner@twitter.com>
Subject: Re: [PATCH 1/3] cache-tree: Create/update cache-tree on checkout
Date: Mon, 30 Jun 2014 11:13:22 -0700 [thread overview]
Message-ID: <xmqqa98uz2nx.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACsJy8D8687QULRBZF_hvwASxOy5ekuPJ997xLSDX6HXDXgZnA@mail.gmail.com> (Duy Nguyen's message of "Sun, 29 Jun 2014 10:33:45 +0700")
Duy Nguyen <pclouds@gmail.com> writes:
> I wonder if we should do this in !opts->force code path only. In the
> opts->force code path we could use prime_cache_tree() (like
> read-tree), which is supposedly faster...
Nobody sane should be constantly running "checkout -f", so even if
priming from existing tree objects were faster, it would be adding
complexity to the code to optimize for a wrong case.
next prev parent reply other threads:[~2014-06-30 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 0:20 [PATCH 1/3] cache-tree: Create/update cache-tree on checkout David Turner
2014-06-28 0:20 ` [PATCH 2/3] test-dump-cache-tree: Improve output format and exit code David Turner
2014-06-28 0:20 ` [PATCH 3/3] cache-tree: Write index with updated cache-tree after commit David Turner
2014-06-30 18:10 ` Junio C Hamano
2014-06-29 3:33 ` [PATCH 1/3] cache-tree: Create/update cache-tree on checkout Duy Nguyen
2014-06-30 18:13 ` Junio C Hamano [this message]
2014-06-30 6:31 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2014-07-01 0:13 David Turner
2014-07-01 4:16 ` Torsten Bögershausen
2014-07-01 19:15 ` David Turner
2014-07-01 21:03 ` Junio C Hamano
2014-07-01 22:09 ` David Turner
2014-07-01 20:15 ` Junio C Hamano
2014-07-06 4:04 ` David Turner
2014-07-07 16:58 ` Junio C Hamano
2014-07-01 19:14 David Turner
2014-07-01 21:08 ` 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=xmqqa98uz2nx.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=dturner@twitter.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=pclouds@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.