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 (Jul 2025, #01; Tue, 1)
Date: Wed, 2 Jul 2025 04:42:49 +0200 [thread overview]
Message-ID: <aGScqbG2SGSK8Hwg@pks.im> (raw)
In-Reply-To: <xmqqwm8rh00m.fsf@gitster.g>
On Tue, Jul 01, 2025 at 06:08:57PM -0700, Junio C Hamano wrote:
> * ps/object-store (2025-07-01) 17 commits
> - odb: rename `read_object_with_reference()`
> - odb: rename `pretend_object_file()`
> - odb: rename `has_object()`
> - odb: rename `repo_read_object_file()`
> - odb: rename `oid_object_info()`
> - odb: trivial refactorings to get rid of `the_repository`
> - odb: get rid of `the_repository` when handling submodule sources
> - odb: get rid of `the_repository` when handling the primary source
> - odb: get rid of `the_repository` in `for_each()` functions
> - odb: get rid of `the_repository` when handling alternates
> - odb: get rid of `the_repository` in `odb_mkstemp()`
> - odb: get rid of `the_repository` in `assert_oid_type()`
> - odb: get rid of `the_repository` in `find_odb()`
> - odb: introduce parent pointers
> - object-store: rename files to "odb.{c,h}"
> - object-store: rename `object_directory` to `odb_source`
> - object-store: rename `raw_object_store` to `object_database`
>
> Code clean-up around object access API.
>
> Comments?
> source: <20250701-pks-object-store-wo-the-repository-v6-0-dbf3894ab4e2@pks.im>
From my point of view this should be good enough now. The only
contentious point really was the renaming of `struct object_directory`.
The current iteration of `struct odb_source` seems to be something that
everyone can agree to, so I don't plan to iterate on this series any
further.
Patrick
next prev parent reply other threads:[~2025-07-02 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 1:08 What's cooking in git.git (Jul 2025, #01; Tue, 1) Junio C Hamano
2025-07-02 2:42 ` Patrick Steinhardt [this message]
2025-07-02 7:16 ` Kristoffer Haugsbakk
2025-07-02 9:25 ` Karthik Nayak
2025-07-03 14:05 ` Re " K Jayatheerth
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=aGScqbG2SGSK8Hwg@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).