On Tue, Feb 02, 2010 at 01:56:41PM +0000, Aneurin Price wrote: > Does anyone have any remarks about these options? Is there a better option - how > difficult would it be to add native support to git? I'm not really familiar with Amazon S3 _or_ the current transport code, but by cursory examination of both, it seems that it would be fairly easy to add support for another transfer. And it might be even better idea to actually just add generic support to invoke an external helper to perform all the heavy lifting. Basically, all the abstraction is already pre-cooked in the form of rsync protocol support. I would just cut'n'paste that and replace rsync magic with simple calls to external helper along some sensible simple API, then code up an easy wrapper for S3 there. Or just add S3 API support directly to core Git - it doesn't seem to be licence-encumbered. Should take just a couple of hours including debugging, if you just copy the existing rsync support functions. Another idea might be to actually use the rsync protocol support itself. ;-) There seems to be some sort of commercial rsync-S3 interface, though I can't tell from their terribly strange pricing policy how expensive it is to use it in practice. -- Petr "Pasky" Baudis If you can't see the value in jet powered ants you should turn in your nerd card. -- Dunbal (464142) -- 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