git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Jan 2026, #09)

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 6, 2026, 19:39 UTC
Message-ID
<xmqq1pixek6j.fsf@gitster.g>
In-Reply-To
<aXk2FjTUMMThs5Kp@nand.local>
Taylor Blau <me@ttaylorr.com> writes:
Show 28 quoted lines
> 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.
Previous: Taylor BlauNext: Derrick Stolee
Message 3 of 8 in “What's cooking in git.git (Jan 2026, #09)”
  1. Junio C HamanoJan 27, 2026
  2. Taylor BlauJan 27, 2026
  3. Junio C HamanoFeb 6, 2026
  4. ds/revision-maximal-only (was Re: What's cooking in git.git (Jan 2026, #09))Derrick Stolee, Jan 28, 2026
  5. brian m. carlsonJan 28, 2026
  6. brian m. carlsonJan 29, 2026
  7. Eric SunshineJan 29, 2026
  8. brian m. carlsonJan 29, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.