Re: [PATCH v5 13/40] external odb: add 'put_raw_obj' support
- Date: Thu, 03 Aug 2017 12:50:27 -0700
- From: Junio C Hamano <gitster@xxxxxxxxx>
- Subject: Re: [PATCH v5 13/40] external odb: add 'put_raw_obj' support
Christian Couder <christian.couder@xxxxxxxxx> writes:
> Add support for a 'put_raw_obj' capability/instruction to send new
> objects to an external odb. Objects will be sent as they are (in
> their 'raw' format). They will not be converted to Git objects.
> For now any new Git object (blob, tree, commit, ...) would be sent
> if 'put_raw_obj' is supported by an odb helper. This is not a great
> default, but let's leave it to following commits to tweak that.
> Signed-off-by: Christian Couder <chriscool@xxxxxxxxxxxxx>
I thought in an earlier step that I saw this thing initialized in
the codepath that adds alternate object stores, which are read-only
places we "borrow" from. Being able to write into it is good, but
conceptually it no longer feels correct to initialize it from the
alternate object database initialization codepath.
Another way to say it is that an object store, whether it is local
or external, is not "alt" if it will result in storing new objects
we locally create. It's just an extension of our local object