From: Duy Nguyen <pclouds@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: "Konstantin Khomoutov" <kostix+git@007spb.ru>,
"Ben Peart" <peartben@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
"Michael Haggerty" <mhagger@alum.mit.edu>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"David Turner" <novalis@novalis.org>,
"Joey Hess" <joey@kitenet.net>,
"Ronnie Sahlberg" <rsahlberg@google.com>,
"Ævar Arnfjörð" <avarab@gmail.com>
Subject: Re: Plugin mechanism(s) for Git?
Date: Sat, 16 Jul 2016 07:31:25 +0200 [thread overview]
Message-ID: <CACsJy8AZak5LyLhLz-6YX0vB8uevKt--Fe9EAMAe1_=14JaaVQ@mail.gmail.com> (raw)
In-Reply-To: <20160715212843.GA5131@dcvr.yhbt.net>
On Fri, Jul 15, 2016 at 11:28 PM, Eric Wong <e@80x24.org> wrote:
> Konstantin Khomoutov <kostix+git@007spb.ru> wrote:
>> Ben Peart <peartben@gmail.com> wrote:
>> > > Lars Schneider wrote:
>> > >
>> > > We could dynamically load libraries but this would force us to
>> > > freeze the ABI as mentioned by Duy:
>> > > http://article.gmane.org/gmane.comp.version-control.git/298463
>> > >
>> >
>> > I wouldn’t be too quick to dismiss dynamically loaded libraries as
>> > there are some distinct advantages over the other patterns especially
>> > performance and simplicity. I realize it requires us to version the
>> > ABI but there are established patterns to manage this. It also isn’t
>> > that much different than us having to freeze or version the protocol
>> > for communicating with a remote-helper.
>
> (re-adding dropped CCs)
>
> The critical difference is protocols can be tested and debugged
> in a language/tool-independent way.
Not using dynamic libraries also makes it possible for other git
reimplementations to reuse the same plugins.
--
Duy
next prev parent reply other threads:[~2016-07-16 5:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 6:46 Plugin mechanism(s) for Git? Christian Couder
2016-07-15 7:37 ` Lars Schneider
2016-07-15 16:18 ` Ben Peart
2016-07-15 16:47 ` Konstantin Khomoutov
2016-07-15 21:28 ` Eric Wong
2016-07-16 5:31 ` Duy Nguyen [this message]
2016-07-16 8:06 ` Jeff King
2016-07-15 8:04 ` Mike Hommey
2016-07-15 8:28 ` Junio C Hamano
2016-07-15 12:18 ` Jeff King
2016-07-15 12:46 ` Ævar Arnfjörð Bjarmason
2016-07-15 13:32 ` Jeff King
2016-07-15 15:52 ` Ben Peart
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='CACsJy8AZak5LyLhLz-6YX0vB8uevKt--Fe9EAMAe1_=14JaaVQ@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joey@kitenet.net \
--cc=kostix+git@007spb.ru \
--cc=mhagger@alum.mit.edu \
--cc=novalis@novalis.org \
--cc=peartben@gmail.com \
--cc=peff@peff.net \
--cc=rsahlberg@google.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.