From: "René Scharfe" <l.s.r@web.de>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2025, #12; Fri, 29)
Date: Sun, 31 Aug 2025 19:29:30 +0200 [thread overview]
Message-ID: <fdee7ee5-21ef-4c5e-92e7-eb92fe07251e@web.de> (raw)
In-Reply-To: <xmqq8qj1n71s.fsf@gitster.g>
On 8/29/25 11:37 PM, Junio C Hamano wrote:
> * rs/describe-with-lazy-queue-and-khash (2025-08-24) 1 commit
> - describe: use khash in finish_depth_computation()
>
> Instead of scanning for the remaining items to see if there are
> still commits to be explored in the queue, use khash to remember
> which items are still on the queue (an unacceptable alternative is
> to reserve one object flag bits).
>
> Will merge to 'next'?
> source: <9110f085-aec0-42e9-9774-b153ece6284f@web.de>
Please keep it in seen for now -- Peff's proposal to use an oidset
instead looks promising. I'll do some more measurements over the next
few days and report back.
René
next prev parent reply other threads:[~2025-08-31 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 21:37 What's cooking in git.git (Aug 2025, #12; Fri, 29) Junio C Hamano
2025-08-31 17:29 ` René Scharfe [this message]
2025-09-02 12:39 ` Jeff King
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=fdee7ee5-21ef-4c5e-92e7-eb92fe07251e@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).