From: Junio C Hamano <gitster@pobox•com>
To: Christian Couder <christian.couder@gmail•com>
Cc: git <git@vger•kernel.org>, "Jeff King" <peff@peff•net>,
"Nguyen Thai Ngoc Duy" <pclouds@gmail•com>,
"Michael Haggerty" <mhagger@alum•mit.edu>,
"Johannes Schindelin" <Johannes.Schindelin@gmx•de>,
"David Turner" <novalis@novalis•org>,
"Ben Peart" <peartben@gmail•com>, "Joey Hess" <joey@kitenet•net>,
"Lars Schneider" <larsxschneider@gmail•com>,
"Ronnie Sahlberg" <rsahlberg@google•com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail•com>
Subject: Re: Plugin mechanism(s) for Git?
Date: Fri, 15 Jul 2016 01:28:31 -0700 [thread overview]
Message-ID: <xmqqd1mfnw40.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAP8UFD1BnnRqsv8zrcDDby=KqQ3UCDVdHWTycfDNTeyfLArn5g@mail.gmail.com> (Christian Couder's message of "Fri, 15 Jul 2016 08:46:03 +0200")
Christian Couder <christian.couder@gmail•com> writes:
> If people think that evolution is better than intelligent design, and
> want each current topic/work to just implement what is best for it,
> then that's ok for me. If on the other hand standardizing on some ways
> to interact with external processes could be helpful to avoid
> duplicating mechanisms/code in slightly different and incompatible
> ways, then I would be happy to discuss it in a thread that is not
> specific to one of the current work.
You seem to have listed only in-flight topics, which may not be a
good starting point to think about the issues. A common trait their
implementation share may not necessarily be a good thing (for one
thing, one trait they share is that none of them is battle tested
yet), so you cannot distill their commonality into something we
would want to have in the first place.
You would need to have existing practices that have worked well for
us in the mix. A few examples that may help the discussion go
forward are the remote-helper framework and credential-helper. They
both call out of Git so that external/third-party enhancement
implementations can do things that core-git alone cannot do
natively.
next prev parent reply other threads:[~2016-07-15 8:28 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
2016-07-16 8:06 ` Jeff King
2016-07-15 8:04 ` Mike Hommey
2016-07-15 8:28 ` Junio C Hamano [this message]
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=xmqqd1mfnw40.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=avarab@gmail$(echo .)com \
--cc=christian.couder@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=joey@kitenet$(echo .)net \
--cc=larsxschneider@gmail$(echo .)com \
--cc=mhagger@alum$(echo .)mit.edu \
--cc=novalis@novalis$(echo .)org \
--cc=pclouds@gmail$(echo .)com \
--cc=peartben@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=rsahlberg@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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