From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Patrick Steinhardt <ps@pks.im>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org, Karthik Nayak <karthik.188@gmail.com>
Subject: Re: Poor performance using reftable with many refs
Date: Thu, 13 Feb 2025 12:12:42 -0800 [thread overview]
Message-ID: <xmqqed01ob7p.fsf@gitster.g> (raw)
In-Reply-To: <20250213194256.GA934256@coredump.intra.peff.net> (Jeff King's message of "Thu, 13 Feb 2025 14:42:56 -0500")
Jeff King <peff@peff.net> writes:
> ... I have trouble
> imagining it helping much beyond something like:
>
> git branch $some_oid
>
> which creates refs/heads/$some_oid. But we probably would be better off
> warning about that at the time of writing rather than checking for
> ambiguity on each read.
Certainly. Thanks for a well thought-out analysis.
next prev parent reply other threads:[~2025-02-13 20:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 0:01 Poor performance using reftable with many refs brian m. carlson
2025-02-13 6:11 ` Patrick Steinhardt
2025-02-13 7:13 ` Patrick Steinhardt
2025-02-13 8:22 ` Jeff King
2025-02-13 11:20 ` Patrick Steinhardt
2025-02-13 14:31 ` Patrick Steinhardt
2025-02-13 19:53 ` Jeff King
2025-02-13 19:42 ` Jeff King
2025-02-13 20:12 ` Junio C Hamano [this message]
2025-02-13 22:17 ` brian m. carlson
2025-02-13 9:27 ` Christian Couder
2025-02-13 13:21 ` Patrick Steinhardt
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=xmqqed01ob7p.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
--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 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.