Re: What's cooking in git.git (Aug 2018, #03; Wed, 15)

From: Duy Nguyen <pclouds@gmail.com>
Date: Aug 17, 2018, 14:56 UTC
Message-ID: <CACsJy8BG+rYx9Epg6vV+q9+A9Kv09RFhR7VGHEqwYw7wt9KXtg@mail.gmail.com>
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:

Show 10 quoted lines

> * 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