From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Derrick Stolee <stolee@gmail.com>
Subject: Re: What's cooking in git.git (Aug 2025, #09; Wed, 20)
Date: Thu, 21 Aug 2025 09:05:26 +0200 [thread overview]
Message-ID: <aKbFNq_pLasQGjbc@pks.im> (raw)
In-Reply-To: <xmqqo6s97e3t.fsf@gitster.g>
On Wed, Aug 20, 2025 at 04:44:22PM -0700, Junio C Hamano wrote:
> * ps/reftable-libgit2-cleanup (2025-08-12) 8 commits
> - refs/reftable: always reload stacks when creating lock
> - reftable: don't second-guess errors from flock interface
> - reftable/stack: handle outdated stacks when compacting
> - reftable/stack: allow passing flags to `reftable_stack_add()`
> - reftable/stack: fix compiler warning due to missing braces
> - reftable/stack: reorder code to avoid forward declarations
> - reftable/writer: drop Git-specific `QSORT()` macro
> - reftable/writer: fix type used for number of records
>
> Code clean-ups.
>
> Will merge to 'next'?
> source: <20250812-pks-reftable-fixes-for-libgit2-v3-0-cf3b2267867e@pks.im>
Yeah, let's merge it down. There's been a couple of reviews for previous
versions, all of which only required minor changes, and the current
version was ACK'd by Justin.
> * 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>
Patrick
next prev parent reply other threads:[~2025-08-21 7:05 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 [this message]
2025-08-28 23:14 ` 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=aKbFNq_pLasQGjbc@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).