From: Junio C Hamano <gitster@pobox•com>
To: shejialuo <shejialuo@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Mar 2025, #02; Thu, 6)
Date: Tue, 11 Mar 2025 10:05:11 -0700 [thread overview]
Message-ID: <xmqq8qpb4hx4.fsf@gitster.g> (raw)
In-Reply-To: <Z9BM4r2CUG1kF_Yo@ArchLinux> (shejialuo@gmail.com's message of "Tue, 11 Mar 2025 22:46:58 +0800")
shejialuo <shejialuo@gmail•com> writes:
> On Thu, Mar 06, 2025 at 04:55:31PM -0800, Junio C Hamano wrote:
>> [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. Any topic outside 'next' would not move until the final
release so it is not urgent (read: if you find a new regression
introduced to 'master' during this cycle and can work on fixing it,
that should take precedence), but if you do have bandwidth to do so
it would be great.
next prev parent reply other threads:[~2025-03-11 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 0:55 What's cooking in git.git (Mar 2025, #02; Thu, 6) Junio C Hamano
2025-03-10 22:09 ` Taylor Blau
2025-03-11 14:46 ` shejialuo
2025-03-11 17:05 ` Junio C Hamano [this message]
2025-03-12 14:09 ` shejialuo
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=xmqq8qpb4hx4.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=shejialuo@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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