Re: [RFC/PATCH v3 00/16] Add initial experimental external ODB support
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 30, 2016, 22:36 UTC
- Message-ID
- <xmqqy400bno3.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <20161130210420.15982-1-chriscool@tuxfamily.org>
Christian Couder <christian.couder@gmail.com> writes:
Show 10 quoted lines
> For now there should be one odb ref per blob. Each ref name should be > refs/odbs/<odbname>/<sha1> where <sha1> is the sha1 of the blob stored > in the external odb named <odbname>. > > These odb refs should all point to a blob that should be stored in the > Git repository and contain information about the blob stored in the > external odb. This information can be specific to the external odb. > The repos can then share this information using commands like: > > `git fetch origin "refs/odbs/<odbname>/*:refs/odbs/<odbname>/*"`
Unless this is designed to serve only a handful of blobs, I cannot see how this design would scale successfully. I notice you wrote "For now" at the beginning, but what is the envisioned way this will evolve in the future?