Re: [PATCH v3] checkout: optimize "git checkout -b <new_branch>"
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 20, 2018, 18:31 UTC
- Message-ID
- <xmqqh8joc2k1.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <CABPp-BGir_5xyqEfwytDog0rZDydPHXjuqXCpNKk67dVPXjUjA@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
Show 8 quoted lines
> == The patch == > - Ben's patch only affects the "checkout -b $NEWBRANCH" case. He > checks for it by looking for any other flag that would be a different > case, and using the old codepath if he finds any. > - This means there is a "giant list of checks" for this optimization, > and an ongoing maintenance burden because if anyone ever adds any > extra options, this optimization might suddenly break things if that > giant list of checks isn't updated.
Correct.
Having said that, I do not mind leaving it in 'pu' for the rest of the cycle, possibly merging it to 'next' after that and keeping it there, to see how horrible a maintenance burden it would become in real life, though.