public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Aaron Plattner <aplattner@nvidia•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org, Jeff King <peff@peff•net>
Subject: Re: What's cooking in git.git (Dec 2025, #03)
Date: Tue, 16 Dec 2025 16:09:30 -0800	[thread overview]
Message-ID: <93afac3c-c532-4183-a1fd-7e2322ee912f@nvidia.com> (raw)
In-Reply-To: <xmqq4ipwc7y2.fsf@gitster.g>

On 12/12/25 2:26 AM, Junio C Hamano wrote:
> * ap/packfile-promisor-object-optim (2025-12-08) 2 commits
>   - packfile: skip hash checks in add_promisor_object()
>   - object: apply skip_hash and discard_tree optimizations to unknown blobs too
> 
>   The code path that enumerates promisor objects have been optimized
>   to skip pointlessly parsing blob objects.
> 
>   Comments?
>   source: <20251209014900.402637-1-aplattner@nvidia•com>
Jeff King said v2 of the patch looked good to him but recommended 
splitting it into two changes. I don't know if he wanted to review v3 or 
if he was okay with it based on his comments on v2. The only differences 
in v3 are the commit count and descriptions.

-- Aaron

  parent reply	other threads:[~2025-12-17  0:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12 10:26 What's cooking in git.git (Dec 2025, #03) Junio C Hamano
2025-12-13  7:42 ` Adrian Ratiu
2025-12-16  1:59   ` Junio C Hamano
2025-12-16  8:13     ` Patrick Steinhardt
2025-12-16 10:41       ` Adrian Ratiu
2025-12-16 17:49         ` Emily Shaffer
2025-12-17  5:04           ` Junio C Hamano
2025-12-13 18:45 ` René Scharfe
2025-12-17  0:09 ` Aaron Plattner [this message]
2025-12-17  5:02   ` Junio C Hamano
2025-12-17  5:20     ` Aaron Plattner
2025-12-17  6:18       ` Jeff King
2025-12-17 13:46       ` Junio C Hamano
2025-12-17 20:26 ` Aaron Plattner
2025-12-18  2:57   ` Junio C Hamano
2025-12-18  6:22     ` 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=93afac3c-c532-4183-a1fd-7e2322ee912f@nvidia.com \
    --to=aplattner@nvidia$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=peff@peff$(echo .)net \
    /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