public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: Patrick Steinhardt <ps@pks•im>
Cc: git@vger•kernel.org,
	 Christian Couder <christian.couder@gmail•com>,
	shejialuo <shejialuo@gmail•com>,
	 Derrick Stolee <stolee@gmail•com>
Subject: Re: What's cooking in git.git (Nov 2024, #07; Wed, 20)
Date: Thu, 21 Nov 2024 10:10:07 +0900	[thread overview]
Message-ID: <xmqqmshtfl3k.fsf@gitster.g> (raw)
In-Reply-To: <Zz27kX159PKAmBOb@pks.im> (Patrick Steinhardt's message of "Wed, 20 Nov 2024 11:36:10 +0100")

Patrick Steinhardt <ps@pks•im> writes:

> On Wed, Nov 20, 2024 at 05:49:34PM +0900, Junio C Hamano wrote:
>> * ps/gc-stale-lock-warning (2024-11-20) 1 commit
> ...
> I'm never quite sure whether I should speak of the command or the code
> unit in this edge case, but this message here seems to indicate that it
> would be preferable to mention the actual command instead.

Either is probably fine, but when the commit describes a fix or an
update to an end-user observable behaviour, the command name would
make a better label to appear in "git shortlog".

>> * ps/send-pack-unhide-error-in-atomic-push (2024-11-15) 6 commits
> ...
> I'll review this patch series later this week.

Thanks.

>> * ps/leakfixes-part-10 (2024-11-13) 28 commits
>> ...
>>  Will merge to 'next'?
>>  source: <20241111-b4-pks-leak-fixes-pt10-v2-0-6154bf91f0b0@pks•im>
>
> Toon left another comment that I'll want to have a look at before
> merging this to "next".

I guess we now have a hopefully final reroll, which I saw and picked
up.

>> * ds/path-walk-1 (2024-11-11) 6 commits
>>  - path-walk: mark trees and blobs as UNINTERESTING
>>  - path-walk: visit tags and cached objects
>>  - path-walk: allow consumer to specify object types
>>  - t6601: add helper for testing path-walk API
>>  - test-lib-functions: add test_cmp_sorted
>>  - path-walk: introduce an object walk by path
>> 
>>  Introduce a new API to visit objects in batches based on a common
>>  path, or by type.
>> 
>>  Comments?
>>  source: <pull.1818.v2.git.1731181272.gitgitgadget@gmail•com>
>
> I think what's interesting in this case is the incompatibility between
> the path-walk API and bitmaps. It seems like there is some push back
> based on this, but from my point of view the path-walk API still has
> uses where bitmaps don't matter that much, like in the proposed new
> git-backfill and git-survey tools. Both of which are of interest to me.

Yup, I didn't have a chance to carefully read what the new code does
yet, and didn't get an impression that anybody did either for v1 or
v2, but I may be mistaken.

>> * cc/promisor-remote-capability (2024-09-10) 4 commits
> ...
> Chris is currently writing such a doc that tries to clarify the bigger
> picture. So I guess we can evict this topic for now, start to discuss
> the vision and then once we're all on the same page start to think
> re-submit the topic.
>
> I've Cc'd him in case he disagrees with me.

Then I'll wait for Christian to speak up.

>> * sj/ref-contents-check (2024-11-15) 9 commits
>> ...
> I've already reviewed this version and expect a (probably final) reroll.

Thanks, I saw that (hopefully) final reroll and picked it up.

Thanks.

next prev parent reply	other threads:[~2024-11-21  1:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20  8:49 What's cooking in git.git (Nov 2024, #07; Wed, 20) Junio C Hamano
2024-11-20 10:36 ` Patrick Steinhardt
2024-11-20 13:41   ` shejialuo
2024-11-21  1:10   ` Junio C Hamano [this message]
2024-11-20 10:39 ` karthik nayak
2024-11-20 16:40 ` Taylor Blau
2024-11-21  0:44   ` Junio C Hamano
2024-11-22  4:34   ` Junio C Hamano
2024-11-21  8:26 ` Kristoffer Haugsbakk
2024-11-21 12:59   ` Junio C Hamano
2024-11-21 15:31     ` Kristoffer Haugsbakk
2024-11-21 23:11       ` Junio C Hamano

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=xmqqmshtfl3k.fsf@gitster.g \
    --to=gitster@pobox$(echo .)com \
    --cc=christian.couder@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=ps@pks$(echo .)im \
    --cc=shejialuo@gmail$(echo .)com \
    --cc=stolee@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox