git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org,  Taylor Blau <me@ttaylorr.com>,
	 Patrick Steinhardt <ps@pks.im>
Subject: Re: ds/path-walk-2 (was Re: What's cooking in git.git (Apr 2025, #03; Fri, 11))
Date: Mon, 14 Apr 2025 05:34:11 -0700	[thread overview]
Message-ID: <xmqqo6wysz0c.fsf@gitster.g> (raw)
In-Reply-To: <7c2b338f-f795-4957-aac3-20e6dd5b5f48@gmail.com> (Derrick Stolee's message of "Mon, 14 Apr 2025 07:03:10 -0400")

Derrick Stolee <stolee@gmail.com> writes:

> On 4/11/2025 6:58 PM, Junio C Hamano wrote:
>
>> * ds/path-walk-2 (2025-03-25) 13 commits
>>  - pack-objects: allow --shallow and --path-walk
>>  - path-walk: add new 'edge_aggressive' option
>>  - pack-objects: thread the path-based compression
>>  - pack-objects: refactor path-walk delta phase
>>  - scalar: enable path-walk during push via config
>>  - pack-objects: enable --path-walk via config
>>  - repack: add --path-walk option
>>  - t5538: add tests to confirm deltas in shallow pushes
>>  - pack-objects: introduce GIT_TEST_PACK_PATH_WALK
>>  - p5313: add performance tests for --path-walk
>>  - pack-objects: update usage to match docs
>>  - pack-objects: add --path-walk option
>>  - pack-objects: extract should_attempt_deltas()
>> 
>>  "git pack-objects" learns to find delta bases from blobs at the
>>  same path, using the --path-walk API.
>> 
>>  Comments?
>>  source: <pull.1819.v2.git.1742829769.gitgitgadget@gmail.com>
> The current version (v2) has not received any comments yet. v1 had
> some, which I responded to, as well as some exploration of the use
> of --window by Taylor. I haven't heard anything since then.

Right.  I do not recall seeing anybody doing a deep dive, which I
would prefer to see done in the code paths involved.  At least I'd
want to see somebody (could be me) verify that the changes would not
break when the new option is not in effect before merging it.

> I continue to get user reports of folks using this feature in Git
> for Windows or microsoft/git, so I still think this would be a
> valuable improvement for the core project.

Oh, no quiestion about that part.  Otherwise we wouldn't be listing
the topic in this list ;-).  I just want to see support not just by
the end-users who do not know or care how the thing looks internally,
but also by the folks around here who do.

Thanks.

      reply	other threads:[~2025-04-14 12:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 22:58 What's cooking in git.git (Apr 2025, #03; Fri, 11) Junio C Hamano
2025-04-12 18:03 ` Philippe Blain
2025-04-13  2:55   ` Philippe Blain
2025-04-14 13:04   ` Junio C Hamano
2025-04-14  8:13 ` Patrick Steinhardt
2025-04-14 13:34   ` Junio C Hamano
2025-04-14 20:14   ` [-SPAM-] " Ramsay Jones
2025-04-14 11:03 ` ds/path-walk-2 (was Re: What's cooking in git.git (Apr 2025, #03; Fri, 11)) Derrick Stolee
2025-04-14 12:34   ` Junio C Hamano [this message]

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=xmqqo6wysz0c.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    --cc=ps@pks.im \
    --cc=stolee@gmail.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).