All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>,
	Elijah Newren <newren@gmail.com>
Subject: Re: What's cooking in git.git (May 2025, #05; Fri, 16)
Date: Mon, 19 May 2025 12:40:34 -0400	[thread overview]
Message-ID: <88fe17b4-9e9c-47df-bb9d-ebd4101503a8@gmail.com> (raw)
In-Reply-To: <xmqqjz6grtbx.fsf@gitster.g>

On 5/16/2025 8:09 PM, Junio C Hamano wrote:

> * ds/sparse-apply-add-p (2025-05-16) 4 commits
>  - p2000: add performance test for patch-mode commands
>  - reset: integrate sparse index with --patch
>  - git add: make -p/-i aware of sparse index
>  - apply: integrate with the sparse index
> 
>  "git apply" and "git add -i/-p" code paths no longer unnecessarily
>  expand sparse-index while working.
> 
>  Will merge to 'next'?
>  Kicked out of next and then is about to come back.
>  source: <pull.1914.v2.git.1747407330.gitgitgadget@gmail.com>

Thanks for applying the latest version. There was good feedback
in the v1 that led to some solid improvements. But I think this
v2 is pretty solid.

> * ds/scalar-no-maintenance (2025-05-14) 5 commits
>  - scalar reconfigure: improve --maintenance docs
>   (merged to 'next' on 2025-05-08 at 1006cdd399)
>  + scalar reconfigure: add --maintenance=<mode> option
>  + scalar clone: add --no-maintenance option
>  + scalar register: add --no-maintenance option
>  + scalar: customize register_dir()'s behavior
> 
>  Two "scalar" subcommands that adds a repository that hasn't been
>  under "scalar"'s control are taught an option not to enable the
>  scheduled maintenance on it.
> 
>  Will merge to 'next' and then to 'master'.
>  source: <pull.1913.v3.git.1746582637.gitgitgadget@gmail.com>

As mentioned in-thread, I'm grateful for your update to include
the last patch.

> * ds/path-walk-2 (2025-05-16) 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.v3.git.1747419124.gitgitgadget@gmail.com>

Thanks for updating to the v3 version. I was a little slow to
respond to Taylor's feedback, so I will not rush feedback on
this version.

Thanks,
-Stolee


      parent reply	other threads:[~2025-05-19 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-17  0:09 What's cooking in git.git (May 2025, #05; Fri, 16) Junio C Hamano
2025-05-17  0:47 ` Elijah Newren
2025-05-18  5:25 ` Aditya Garg
2025-05-19 16:40 ` Derrick Stolee [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=88fe17b4-9e9c-47df-bb9d-ebd4101503a8@gmail.com \
    --to=stolee@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    --cc=newren@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.