Re: Plugin mechanism(s) for Git?

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 15, 2016, 08:28 UTC
Message-ID: <xmqqd1mfnw40.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAP8UFD1BnnRqsv8zrcDDby=KqQ3UCDVdHWTycfDNTeyfLArn5g@mail.gmail.com>

Christian Couder <christian.couder@gmail.com> writes:

Show 7 quoted lines

> 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.