Re: RFC: a plugin architecture for git extensions?
- From
- david@lang.hm <david@lang.hm>
- Date
- Apr 28, 2011, 16:16 UTC
- Message-ID
- <alpine.DEB.2.00.1104280915230.7120@asgard.lang.hm>
- In-Reply-To
- <BANLkTimyFmujc+Lsd7DMWfJgUzZME+Sveg@mail.gmail.com>
On Thu, 28 Apr 2011, Jon Seymour wrote:
Show 16 quoted lines
> On Thu, Apr 28, 2011 at 3:07 AM, A Large Angry SCM <gitzilla@gmail.com> wrote:
>>
>> For a git plugin ecosystem to work, a (relatively) stable API/ABI is
>> necessary for the plugin authors to code to. Where is your proposal for
>> that.
>>
>
> To answer your question, the intent is to provide plugins git's
> command line interface.
>
> As has already explained by Junio amongst others, git already provides
> support for such extensions via its idiom of treating any executable
> of the form git-{command} found in the PATH.
>
> The intention of my proposal is simply to formalise the plugin
> architecture and provide a degree of plugin management.start with documenting (and therefor formalizing) how plugins can work today. Then propose your change to how they work, what the benifits of your change are, and the code needed to implement your change.
David Lang
Show 9 quoted lines
> Of course, others might think there is a need for ABI plugins, and > they are free to propose such extensions, but that is not my intent. > > jon. > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >