git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] [RFC] Revert/delay performance regression in 'git checkout -b'

From
Derrick Stolee <stolee@gmail.com>
Date
Aug 22, 2019, 13:43 UTC
Message-ID
<0c3bdcb6-d742-0182-b8b2-8f12a5b718b3@gmail.com>
In-Reply-To
<20190821223158.GB20404@szeder.dev>
On 8/21/2019 6:31 PM, SZEDER Gábor wrote:
Show 16 quoted lines
> On Wed, Aug 21, 2019 at 12:18:32PM -0700, Derrick Stolee via GitGitGadget wrote:
>> As we were integrating Git 2.23.0 into VFS for Git, we discovered that "git
>> checkout -b new-branch" went from 0.3s to 10+s on the Windows OS repo.
> 
> Does this slowdown only affect the Windows OS repo with VFS for Git,
> or other biggish repos without VFS for Git as well?
> 
>> This series does the following:
>>
>>  1. Reverts the change that makes 'git checkout -b' slow again.
>>  2. Creates a warning that recommends users start using 'git switch -c'
>>     instead.
> 
> 'git help switch' says loudly and clearly that "THIS COMMAND IS
> EXPERIMENTAL. THE BEHAVIOR MAY CHANGE."  It's too early to recommend
> it this aggressively, and to deprecate any parts of 'git checkout'.

Even more reason why the performance boost should not have been removed from 'git checkout -b' so quickly.

Thanks, -Stolee

Previous: Elijah NewrenNext: Elijah Newren
Message 9 of 11 in “[RFC] Revert/delay performance regression in 'git checkout -b'”
  1. 0/2 [RFC] Revert/delay performance regression in 'git checkout -b'Derrick Stolee via GitGitGadget, Aug 21, 2019
  2. 1/2 Revert "switch: no worktree status unless real branch switch happens"Derrick Stolee via GitGitGadget, Aug 21, 2019
  3. SZEDER GáborAug 21, 2019
  4. Derrick StoleeAug 22, 2019
  5. 2/2 DEPRECATION: warn about 'git checkout -b'Derrick Stolee via GitGitGadget, Aug 21, 2019
  6. Elijah NewrenAug 22, 2019
  7. SZEDER GáborAug 21, 2019
  8. Elijah NewrenAug 22, 2019
  9. Derrick StoleeAug 22, 2019
  10. Elijah NewrenAug 22, 2019
  11. Derrick StoleeAug 22, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.