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

Re: What's cooking in git.git (Mar 2025, #02; Thu, 6)

From
shejialuo <shejialuo@gmail.com>
Date
Mar 11, 2025, 14:46 UTC
Message-ID
<Z9BM4r2CUG1kF_Yo@ArchLinux>
In-Reply-To
<xmqqzfhxfym4.fsf@gitster.g>
On Thu, Mar 06, 2025 at 04:55:31PM -0800, Junio C Hamano wrote:
Show 25 quoted lines
> [Cooking]
> * ps/refname-avail-check-optim (2025-03-06) 16 commits
>  - refs: reuse iterators when determining refname availability
>  - refs/iterator: implement seeking for files iterators
>  - refs/iterator: implement seeking for packed-ref iterators
>  - refs/iterator: implement seeking for ref-cache iterators
>  - refs/iterator: implement seeking for reftable iterators
>  - refs/iterator: implement seeking for merged iterators
>  - refs/iterator: provide infrastructure to re-seek iterators
>  - refs/iterator: separate lifecycle from iteration
>  - refs: stop re-verifying common prefixes for availability
>  - refs/files: batch refname availability checks for initial transactions
>  - refs/files: batch refname availability checks for normal transactions
>  - refs/reftable: batch refname availability checks
>  - refs: introduce function to batch refname availability checks
>  - builtin/update-ref: skip ambiguity checks when parsing object IDs
>  - object-name: allow skipping ambiguity checks in `get_oid()` family
>  - object-name: introduce `repo_get_oid_with_flags()`
>  (this branch is used by kn/non-transactional-batch-updates.)
> 
>  The code paths to check whether a refname X is available (by seeing
>  if another ref X/Y exists, etc.) have been optimized.
> 
>  Needs review.
>  source: <20250306-pks-update-ref-optimization-v5-0-dcb2ee037e97@pks.im>

I have reviewed some patches for the earlier version. This week, if I have bandwidth, I would review the whole patches again for this version.

Thanks, Jialuo

Previous: Taylor BlauNext: Junio C Hamano
Message 3 of 5 in “What's cooking in git.git (Mar 2025, #02; Thu, 6)”
  1. Junio C HamanoMar 7, 2025
  2. Taylor BlauMar 10, 2025
  3. shejialuoMar 11, 2025
  4. Junio C HamanoMar 11, 2025
  5. shejialuoMar 12, 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.