From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Ben Peart <Ben.Peart@microsoft.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2018, #03; Wed, 15)
Date: Fri, 17 Aug 2018 16:56:09 +0200 [thread overview]
Message-ID: <CACsJy8BG+rYx9Epg6vV+q9+A9Kv09RFhR7VGHEqwYw7wt9KXtg@mail.gmail.com> (raw)
In-Reply-To: <xmqqpnyjgroj.fsf@gitster-ct.c.googlers.com>
On Thu, Aug 16, 2018 at 1:01 AM Junio C Hamano <gitster@pobox.com> wrote:
> * bp/checkout-new-branch-optim (2018-07-31) 1 commit
> - checkout: optimize "git checkout -b <new_branch>"
>
> "git checkout -b newbranch [HEAD]" should not have to do as much as
> checking out a commit different from HEAD. An attempt is made to
> optimize this special case.
>
> So... what is the status of this thing? Is the other "optimize
> unpack-trees" effort turning out to be a safer and less hacky way
> to achieve similar gain and this no longer is needed?
I still dislike the fact that this depends on config keys to tweak
behavior and believe there are still rooms for general optimizations.
But the feeling I have so far is I'm doing all the work for Microsoft
in that direction. So I give up. It's up to you and Ben to decide.
--
Duy
prev parent reply other threads:[~2018-08-17 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 23:01 What's cooking in git.git (Aug 2018, #03; Wed, 15) Junio C Hamano
2018-08-16 2:35 ` Stefan Beller
2018-08-16 14:58 ` Junio C Hamano
2018-08-16 13:15 ` Derrick Stolee
2018-08-16 14:43 ` Stefan Beller
2018-08-17 14:56 ` Duy Nguyen [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACsJy8BG+rYx9Epg6vV+q9+A9Kv09RFhR7VGHEqwYw7wt9KXtg@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=Ben.Peart@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).