The series introduces an object storage extension similar in spirit and design to the ref storage extension. It is configured through extensions.objectStorage with the syntax "<schema>[://<payload>]". The usual mechanisms are provided: --object-storage-format=, GIT_OBJECT_STORAGE_FORMAT, GIT_DEFAULT_OBJECT_STORAGE_FORMAT and an init.default setting for the format.
Only the "files" format is supported, so little changes in behavior. The optional payload, however, lets users configure a different location for the .git/objects directory.
Karthik Nayak reviewed the patches and said that apart from nits, which he said could be ignored, the series looks good. His nits included dropping a 'Likewise' in a comment, avoiding wording that makes the default look like one of the backends, and a stray newline.
Patrick explained why the payload is there. It lets pluggable object databases and the format extension be tested together with a payload, and it matches the ref storage format, where the location can also be configured. He added that GitLab has a use for it as a building block for migrations, and said he would adapt the commit message.
He also kept the OBJECT_STORAGE_FORMAT_UNKNOWN enum value, because dropping it would require a special case for a NULL value. A wrong diff header in one review comment turned out to be a mix-up, and he has fixed the issue in setup.c. He said he would wait a bit and send a new version the next morning.