git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
	"D. Ben Knoble" <ben.knoble@gmail.com>,
	Emily Shaffer <nasamuffin@google.com>,
	Christian Fredrik Johnsen <cfj@johnsen.no>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [Feature Request] Allow batch removal of remotes with 'git remote remove'
Date: Wed, 22 Jan 2025 10:40:17 +0100	[thread overview]
Message-ID: <Z5C9AcABPMz6OFRd@pks.im> (raw)
In-Reply-To: <Z5BW5ofJVbM1obb5@tapette.crustytoothpaste.net>

On Wed, Jan 22, 2025 at 02:24:38AM +0000, brian m. carlson wrote:
> [0] Sometime back I reported that `git remote rename` on a fresh clone
> with 45,000 refs took about 45 minutes.  The reason I didn't choose the
> remote name on the original clone (with `-o`) is because it was in a
> GitHub Codespace, which had cloned it for me already.  Fortunately, this
> is now down to about 55 to 78 seconds with reftable, which is a major
> improvement, and I'm sure we could do better still.

That's awesome. Thanks a lot for playing around with reftables and
reporting your bugs and findings, I really appreciate it. This kind of
information is invaluable to us.

Patrick

      parent reply	other threads:[~2025-01-22  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 23:06 [Feature Request] Allow batch removal of remotes with 'git remote remove' Christian Fredrik Johnsen
2025-01-21 21:10 ` Emily Shaffer
2025-01-21 21:32   ` D. Ben Knoble
2025-01-21 22:38     ` Junio C Hamano
2025-01-22  2:24     ` brian m. carlson
2025-01-22  3:08       ` Jeff King
2025-01-22 16:23         ` Junio C Hamano
2025-01-22  9:40       ` Patrick Steinhardt [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z5C9AcABPMz6OFRd@pks.im \
    --to=ps@pks.im \
    --cc=ben.knoble@gmail.com \
    --cc=cfj@johnsen.no \
    --cc=git@vger.kernel.org \
    --cc=nasamuffin@google.com \
    --cc=sandals@crustytoothpaste.net \
    /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 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 NNTP newsgroup(s).