From: Klein W <wineklein@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: remote helper example with push/fetch capabilities
Date: Mon, 15 Dec 2014 16:42:56 -0500 [thread overview]
Message-ID: <CAPCWLt4=oYTPFXktCj8CgqNncaO2=sbwZcPOVa+a5wgt7HPCUQ@mail.gmail.com> (raw)
In-Reply-To: <20141215204740.GI29365@google.com>
On Mon, Dec 15, 2014 at 3:47 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Sure --- see remote-curl.c.
>
> There's also the "connect" capability. builtin/remote-ext.c and
> builtin/remote-fd.c are examples using that one.
Thanks.
>> Also, what are the advantages and disadvantages of a remote helper
>> with push/fetch capabilities vs a remote helper with import/export
>> capabilities?
>
> 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?
Thanks.
next prev parent reply other threads:[~2014-12-15 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 20:17 remote helper example with push/fetch capabilities Klein W
2014-12-15 20:47 ` Jonathan Nieder
2014-12-15 21:42 ` Klein W [this message]
2014-12-15 21:44 ` Jonathan Nieder
2014-12-15 22:41 ` Klein W
2014-12-18 21:46 ` Klein W
2014-12-15 21:47 ` Junio C Hamano
2015-01-14 21:57 ` Andrew Mackenzie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPCWLt4=oYTPFXktCj8CgqNncaO2=sbwZcPOVa+a5wgt7HPCUQ@mail.gmail.com' \
--to=wineklein@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).