On Tue, Jun 07, 2016 at 10:46:07AM +0200, Christian Couder wrote: > The high level overview of the patch series I would like to send > really soon now could go like this: > > --- > Git can store its objects only in the form of loose objects in > separate files or packed objects in a pack file. > To be able to better handle some kind of objects, for example big > blobs, it would be nice if Git could store its objects in other object > databases (ODB). > > To do that, this patch series makes it possible to register commands, > using "odb.<odbname>.command" config variables, to access external > ODBs. Each specified command will then be called the following ways: > > - "<command> have": the command should output the sha1, size and > type of all the objects the external ODB contains, one object per > line. > - "<command> get <sha1>": the command should then read from the > external ODB the content of the object corresponding to <sha1> and > output it on stdout. > - "<command> put <sha1> <size> <type>": the command should then read > from stdin an object and store it in the external ODB. (disclaimer: I didn't look at the patch series) Does this mean you're going to fork/exec() a new <command> for each of these? It would probably be better if it was "batched", where the executable is invoked once and the commands are passed to its stdin. Mike -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html