From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, pclouds@gmail.com, git@jeffhostetler.com,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/2] [RFC] Revert/delay performance regression in 'git checkout -b'
Date: Thu, 22 Aug 2019 00:31:59 +0200 [thread overview]
Message-ID: <20190821223158.GB20404@szeder.dev> (raw)
In-Reply-To: <pull.317.git.gitgitgadget@gmail.com>
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'.
next prev parent reply other threads:[~2019-08-21 22:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 19:18 [PATCH 0/2] [RFC] Revert/delay performance regression in 'git checkout -b' Derrick Stolee via GitGitGadget
2019-08-21 19:18 ` [PATCH 1/2] Revert "switch: no worktree status unless real branch switch happens" Derrick Stolee via GitGitGadget
2019-08-21 22:15 ` SZEDER Gábor
2019-08-22 13:41 ` Derrick Stolee
2019-08-21 19:18 ` [PATCH 2/2] DEPRECATION: warn about 'git checkout -b' Derrick Stolee via GitGitGadget
2019-08-22 3:03 ` Elijah Newren
2019-08-21 22:31 ` SZEDER Gábor [this message]
2019-08-22 3:18 ` [PATCH 0/2] [RFC] Revert/delay performance regression in " Elijah Newren
2019-08-22 13:43 ` Derrick Stolee
2019-08-22 3:16 ` Elijah Newren
2019-08-22 13:45 ` Derrick Stolee
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=20190821223158.GB20404@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--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.