From: Junio C Hamano <gitster@pobox.com>
To: Klein W <wineklein@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: remote helper example with push/fetch capabilities
Date: Mon, 15 Dec 2014 13:47:20 -0800 [thread overview]
Message-ID: <xmqqegs0d1qv.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAPCWLt6kxoJJSWAcyH_kW071Md0vc4zeo41hCKBQHd-_pvUMXQ@mail.gmail.com> (Klein W.'s message of "Mon, 15 Dec 2014 15:17:24 -0500")
Klein W <wineklein@gmail.com> writes:
> Is there any example of a remote helper [0] with push and fetch capabilities?
>
> The git-remote-testgit.sh example [1] only has import/export capabilities.
>
> Also, what are the advantages and disadvantages of a remote helper
> with push/fetch capabilities vs a remote helper with import/export
> capabilities?
A helper with push/fetch capabilities is responsible for (and more
importantly, "in control of") packdata creation, while helpers that
use import/export interface rely on fast-import, which is quite dumb
when it comes to storage efficiency of the resulting repository.
The former might be more preferrable from the efficiency point of
view.
BUT.
Unless your foreign SCM is Git itself, however, it is not practical
to write your own pack data generator correctly and efficiently to
support push/fetch capabilities anyway, so the choice is often made
not because of "advantages vs disadvantages" but because of what you
can write in practice.
next prev parent reply other threads:[~2014-12-15 21:47 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
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 [this message]
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=xmqqegs0d1qv.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=wineklein@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.