Re: [RFC/PATCH v4 00/49] Add initial experimental external ODB support

From: Christian Couder <christian.couder@gmail.com>
Date: Jun 20, 2017, 13:48 UTC
Message-ID: <CAP8UFD2S21er8U8KA6MBfu5uES5iNd8zV0=wcVNtAbKv5wVpuQ@mail.gmail.com>
In-Reply-To: <20170620075523.26961-1-chriscool@tuxfamily.org>

On Tue, Jun 20, 2017 at 9:54 AM, Christian Couder <christian.couder@gmail.com> wrote:

Show 14 quoted lines

>
> Future work
> ~~~~~~~~~~~
>
> First sorry about the state of this patch series, it is not as clean
> as I would have liked, butI think it is interesting to get feedback
> from the mailing list at this point, because the previous RFC was sent
> a long time ago and a lot of things changed.
>
> So a big part of the future work will be about cleaning this patch series.
>
> Other things I think I am going to do:
>
>   -

Ooops, I had not save my emacs buffer where I wrote this when I sent the patch series.

This should have been:

Other things I think I may work on:

  - Remove the "odb.<odbname>.scriptMode" and "odb.<odbname>.command"
    options and instead have just "odb.<odbname>.scriptCommand" and
    "odb.<odbname>.subprocessCommand".

  - Use capabilities instead of "odb.<odbname>.fetchKind" to decide
    which kind of "get" will be used.

  - Better test all the combinations of the above modes with and
    without "have" and "put" instructions.

  - Maybe also have different kinds of "put" so that Git could pass
    either a git object a plain object or ask the helper to retreive
    it directly from Git's object database.

  - Maybe add an "init" instruction as the script mode has something
    like this called "get_cap" and it would help the sub-process mode
    too, as it makes it possible for Git to know the capabilities
    before trying to send any instruction (that might not be supported
    by the helper). The "init" instruction would be the only required
    instruction for any helper to implement.

  - Add more long running tests and improve tests in general.