From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: What's cooking in git.git (Aug 2025, #09; Wed, 20)
Date: Thu, 28 Aug 2025 16:14:39 -0700 [thread overview]
Message-ID: <xmqq4itrrqcg.fsf@gitster.g> (raw)
In-Reply-To: <aKbFNq_pLasQGjbc@pks.im> (Patrick Steinhardt's message of "Thu, 21 Aug 2025 09:05:26 +0200")
Patrick Steinhardt <ps@pks.im> writes:
>> * ps/object-store-midx-dedup-info (2025-08-11) 11 commits
>> - midx: compute paths via their source
>> - midx: stop duplicating info redundant with its owning source
>> - midx: write multi-pack indices via their source
>> - midx: load multi-pack indices via their source
>> - midx: drop redundant `struct repository` parameter
>> - odb: simplify calling `link_alt_odb_entry()`
>> - odb: return newly created in-memory sources
>> - odb: consistently use "dir" to refer to alternate's directory
>> - odb: allow `odb_find_source()` to fail
>> - odb: store locality in object database sources
>> - Merge branch 'ps/object-store-midx' into ps/object-store-midx-dedup-info
>>
>> Further code clean-up for multi-pack-index code paths.
>>
>> Will merge to 'next'?
>> source: <20250811-b4-pks-midx-deduplicate-source-info-v3-0-e442bdf2b4ad@pks.im>
>
> There's still an outstanding question for Stolee [1] regarding the
> `--object-dir` option of git-multi-pack-index(1). It would be nice to
> give him a copule of days more to chime in. I've Cc'd him now.
>
> [1]: <aJUn0qeliNQ/nnWr@nand.local>
Then let me give a gentle ping here...
prev parent reply other threads:[~2025-08-28 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 23:44 What's cooking in git.git (Aug 2025, #09; Wed, 20) Junio C Hamano
2025-08-21 7:05 ` Patrick Steinhardt
2025-08-28 23:14 ` 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=xmqq4itrrqcg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).