From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, Karthik Nayak <karthik.188@gmail.com>
Subject: Re: [PATCH v3 2/7] setup: introduce object storage extension
Date: Sat, 24 Oct 2026 16:50:20 +0200 [thread overview]
Message-ID: <atzFrKoU/mrhq31L@szeder.dev> (raw)
In-Reply-To: <20261023-b4-pks-odb-extension-v3-2-b1bb30a006db@pks.im>
On Fri, Oct 23, 2026 at 01:49:11PM +0200, Patrick Steinhardt wrote:
> Introduce a new "extensions.objectStorage" extension that allows the
> user to configure the primary object database source of a repository.
> The value is a URI in the format "<schema>[://<payload>]", mirroring
> the format used by "extensions.refStorage":
>
> - The schema identifies the backend that shall be used. For now the
> only supported schema is "files", which is the existing object
> database backed by loose objects and packfiles.
>
> - The payload can be passed to configure the backend, and its
> interpretation is backend-specific. For the "files" backend, it
> allows you to configure a different location for the ".git/objects"
> directory.
Please justify why you want to make this configurable.
next prev parent reply other threads:[~2026-10-24 14:50 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 8:55 [PATCH 0/7] odb: introduce object storage extension Patrick Steinhardt
2026-10-19 8:55 ` [PATCH 1/7] loose: drop unused `repo_write_loose_object_map()` Patrick Steinhardt
2026-10-19 20:21 ` Karthik Nayak
2026-10-20 8:49 ` Patrick Steinhardt
2026-10-20 18:30 ` Karthik Nayak
2026-10-19 8:55 ` [PATCH 2/7] setup: introduce object storage extension Patrick Steinhardt
2026-10-19 21:29 ` Karthik Nayak
2026-10-20 1:27 ` Junio C Hamano
2026-10-20 18:32 ` Karthik Nayak
2026-10-20 8:50 ` Patrick Steinhardt
2026-10-20 19:06 ` Karthik Nayak
2026-10-19 8:55 ` [PATCH 3/7] setup: allow overriding object storage format via environment Patrick Steinhardt
2026-10-19 21:34 ` Karthik Nayak
2026-10-20 8:50 ` Patrick Steinhardt
2026-10-20 19:08 ` Karthik Nayak
2026-10-19 8:55 ` [PATCH 4/7] builtin: expose the object storage format Patrick Steinhardt
2026-10-19 21:40 ` Karthik Nayak
2026-10-20 8:50 ` Patrick Steinhardt
2026-10-20 19:10 ` Karthik Nayak
2026-10-19 8:56 ` [PATCH 5/7] builtin/init: introduce handling of " Patrick Steinhardt
2026-10-19 8:56 ` [PATCH 6/7] builtin/clone: introduce "--object-storage-format=" Patrick Steinhardt
2026-10-19 8:56 ` [PATCH 7/7] builtin/submodule: propagate "--object-storage-format=" Patrick Steinhardt
2026-10-21 5:39 ` [PATCH v2 0/7] odb: introduce object storage extension Patrick Steinhardt
2026-10-21 5:39 ` [PATCH v2 1/7] loose: drop unused `repo_write_loose_object_map()` Patrick Steinhardt
2026-10-21 5:39 ` [PATCH v2 2/7] setup: introduce object storage extension Patrick Steinhardt
2026-10-21 5:39 ` [PATCH v2 3/7] setup: allow overriding object storage format via environment Patrick Steinhardt
2026-10-21 5:39 ` [PATCH v2 4/7] builtin: expose the object storage format Patrick Steinhardt
2026-10-21 5:39 ` [PATCH v2 5/7] builtin/init: introduce handling of " Patrick Steinhardt
2026-10-21 14:23 ` Karthik Nayak
2026-10-23 5:33 ` Patrick Steinhardt
2026-10-21 5:39 ` [PATCH v2 6/7] builtin/clone: introduce "--object-storage-format=" Patrick Steinhardt
2026-10-21 5:39 ` [PATCH v2 7/7] builtin/submodule: propagate "--object-storage-format=" Patrick Steinhardt
2026-10-21 14:31 ` [PATCH v2 0/7] odb: introduce object storage extension Karthik Nayak
2026-10-23 11:49 ` [PATCH v3 " Patrick Steinhardt
2026-10-23 11:49 ` [PATCH v3 1/7] loose: drop unused `repo_write_loose_object_map()` Patrick Steinhardt
2026-10-23 11:49 ` [PATCH v3 2/7] setup: introduce object storage extension Patrick Steinhardt
2026-10-24 14:50 ` SZEDER Gábor [this message]
2026-10-26 10:05 ` Patrick Steinhardt
2026-10-26 11:22 ` Karthik Nayak
2026-10-26 11:53 ` Patrick Steinhardt
2026-10-23 11:49 ` [PATCH v3 3/7] setup: allow overriding object storage format via environment Patrick Steinhardt
2026-10-26 11:25 ` Karthik Nayak
2026-10-26 11:53 ` Patrick Steinhardt
2026-10-23 11:49 ` [PATCH v3 4/7] builtin: expose the object storage format Patrick Steinhardt
2026-10-23 11:49 ` [PATCH v3 5/7] builtin/init: introduce handling of " Patrick Steinhardt
2026-10-23 11:49 ` [PATCH v3 6/7] builtin/clone: introduce "--object-storage-format=" Patrick Steinhardt
2026-10-23 11:49 ` [PATCH v3 7/7] builtin/submodule: propagate "--object-storage-format=" Patrick Steinhardt
2026-10-26 11:35 ` [PATCH v3 0/7] odb: introduce object storage extension Karthik Nayak
2026-10-26 11:53 ` Patrick Steinhardt
2026-10-27 6:59 ` [PATCH v4 " Patrick Steinhardt
2026-10-27 6:59 ` [PATCH v4 1/7] loose: drop unused `repo_write_loose_object_map()` Patrick Steinhardt
2026-10-27 6:59 ` [PATCH v4 2/7] setup: introduce object storage extension Patrick Steinhardt
2026-10-27 6:59 ` [PATCH v4 3/7] setup: allow overriding object storage format via environment Patrick Steinhardt
2026-10-27 6:59 ` [PATCH v4 4/7] builtin: expose the object storage format Patrick Steinhardt
2026-10-27 6:59 ` [PATCH v4 5/7] builtin/init: introduce handling of " Patrick Steinhardt
2026-10-27 6:59 ` [PATCH v4 6/7] builtin/clone: introduce "--object-storage-format=" Patrick Steinhardt
2026-10-27 6:59 ` [PATCH v4 7/7] builtin/submodule: propagate "--object-storage-format=" Patrick Steinhardt
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=atzFrKoU/mrhq31L@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/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