From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2025, #01; Mon, 3)
Date: Tue, 4 Nov 2025 07:11:52 +0100 [thread overview]
Message-ID: <aQmZKCUH-SXjZONV@pks.im> (raw)
In-Reply-To: <xmqqseevt4gf.fsf@gitster.g>
On Mon, Nov 03, 2025 at 09:24:00AM -0800, Junio C Hamano wrote:
> * ps/object-source-loose (2025-10-30) 13 commits
> - object-file: refactor writing objects via a stream
> - object-file: rename `write_object_file()`
> - object-file: refactor freshening of objects
> - object-file: rename `has_loose_object()`
> - object-file: read objects via the loose object source
> - object-file: move loose object map into loose source
> - object-file: hide internals when we need to reprepare loose sources
> - object-file: move loose object cache into loose source
> - object-file: introduce `struct odb_loose_source`
> - object-file: move `fetch_if_missing`
> - odb: adjust naming to free object sources
> - odb: introduce `odb_source_new()`
> - odb: fix subtle logic to check whether an alternate is usable
>
> A part of code paths that deals with loose objects has been cleaned
> up.
>
> Will merge to 'next'?
> source: <20251031-b4-pks-odb-loose-backend-v2-0-920f721aef71@pks.im>
This still seems to be using v2, and I've since sent v3 that renames
`struct odb_loose_source` to `struct odb_source_loose`. But that version
should be ready for "next" indeed.
Thanks!
Patrick
prev parent reply other threads:[~2025-11-04 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 17:24 What's cooking in git.git (Nov 2025, #01; Mon, 3) Junio C Hamano
2025-11-04 6:11 ` Patrick Steinhardt [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=aQmZKCUH-SXjZONV@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).