Re: remote helper example with push/fetch capabilities

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Dec 15, 2014, 21:44 UTC
Message-ID: <20141215214459.GJ29365@google.com>
In-Reply-To: <CAPCWLt4=oYTPFXktCj8CgqNncaO2=sbwZcPOVa+a5wgt7HPCUQ@mail.gmail.com>

Klein W wrote:

> On Mon, Dec 15, 2014 at 3:47 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:

Show 12 quoted lines

>> It mainly has to do with what it is convenient for your helper to
>> produce.  If the helper would find it more convenient to write native
>> git objects (for example because the remote server speaks a
>> git-specific protocol, as in the case of remote-curl.c) then the
>> "fetch" capability will be more convenient.  If the helper wants to
>> make a batch of new objects then a fast-import stream can be a
>> convenient way to do this and the "import" capability takes care of
>> running fast-import to take care of that.
>
> I'm trying to write a remote helper for hosting git remotes on Amazon
> S3.  Do you have any intuition about which capabilities would work
> best for this case?

fetch/push. I'd suggest looking at the "dumb" HTTP code (fetch_dumb, push_dav) in remote-curl.c to start.

Thanks, Jonathan