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

Re: Poor performance using reftable with many refs

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 13, 2025, 20:12 UTC
Message-ID
<xmqqed01ob7p.fsf@gitster.g>
In-Reply-To
<20250213194256.GA934256@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 8 quoted lines
> ... 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.
Previous: Jeff KingNext: brian m. carlson
Message 9 of 12 in “Poor performance using reftable with many refs”
  1. brian m. carlsonFeb 13, 2025
  2. Patrick SteinhardtFeb 13, 2025
  3. Patrick SteinhardtFeb 13, 2025
  4. Jeff KingFeb 13, 2025
  5. Patrick SteinhardtFeb 13, 2025
  6. Patrick SteinhardtFeb 13, 2025
  7. Jeff KingFeb 13, 2025
  8. Jeff KingFeb 13, 2025
  9. Junio C HamanoFeb 13, 2025
  10. brian m. carlsonFeb 13, 2025
  11. Christian CouderFeb 13, 2025
  12. Patrick SteinhardtFeb 13, 2025

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.