From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Junio C Hamano <junio@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2026, #09)
Date: Fri, 06 Feb 2026 11:39:00 -0800 [thread overview]
Message-ID: <xmqq1pixek6j.fsf@gitster.g> (raw)
In-Reply-To: <aXk2FjTUMMThs5Kp@nand.local> (Taylor Blau's message of "Tue, 27 Jan 2026 17:03:02 -0500")
Taylor Blau <me@ttaylorr.com> writes:
> On Tue, Jan 27, 2026 at 09:42:00AM -0800, Junio C Hamano wrote:
>> * ps/odb-for-each-object (2026-01-26) 16 commits
>> - odb: drop unused `for_each_{loose,packed}_object()` functions
>> - reachable: convert to use `odb_for_each_object()`
>> - builtin/pack-objects: use `packfile_store_for_each_object()`
>> - odb: introduce mtime fields for object info requests
>> - treewide: drop uses of `for_each_{loose,packed}_object()`
>> - treewide: enumerate promisor objects via `odb_for_each_object()`
>> - builtin/fsck: refactor to use `odb_for_each_object()`
>> - odb: introduce `odb_for_each_object()`
>> - packfile: introduce function to iterate through objects
>> - packfile: extract function to iterate through objects of a store
>> - object-file: introduce function to iterate through objects
>> - object-file: extract function to read object info from path
>> - odb: fix flags parameter to be unsigned
>> - odb: rename `FOR_EACH_OBJECT_*` flags
>> - Merge branch 'ps/packfile-store-in-odb-source' into ps/odb-for-each-object
>> - Merge branch 'ps/read-object-info-improvements' into ps/odb-for-each-object
>>
>> Revamp object enumeration API around odb.
>>
>> Will merge to 'next'?
>> source: <20260126-pks-odb-for-each-object-v4-0-5a64a038c791@pks.im>
>
> I have some lingering questions about the mtime-related changes. I am
> not opposed to the series in general, but I think some more time to
> continue the discussion in that thread would be beneficial before
> starting to merge it down.
Has any further discussions took place outside the original thread
https://lore.kernel.org/git/20260126-pks-odb-for-each-object-v4-0-5a64a038c791@pks.im/
or are we pretty much done with this iteration and polish
incrementally if necessary?
Thanks.
next prev parent reply other threads:[~2026-02-06 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 17:42 What's cooking in git.git (Jan 2026, #09) Junio C Hamano
2026-01-27 22:03 ` Taylor Blau
2026-02-06 19:39 ` Junio C Hamano [this message]
2026-01-28 14:29 ` ds/revision-maximal-only (was Re: What's cooking in git.git (Jan 2026, #09)) Derrick Stolee
2026-01-28 22:50 ` What's cooking in git.git (Jan 2026, #09) brian m. carlson
2026-01-29 22:01 ` brian m. carlson
2026-01-29 22:51 ` Eric Sunshine
2026-01-29 23:25 ` brian m. carlson
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=xmqq1pixek6j.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=junio@pobox.com \
--cc=me@ttaylorr.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