Re: RFC: a plugin architecture for git extensions?
- From
Jon Seymour <jon.seymour@gmail.com>
- Date
- Apr 28, 2011, 03:07 UTC
- Message-ID
- <BANLkTimyFmujc+Lsd7DMWfJgUzZME+Sveg@mail.gmail.com>
- In-Reply-To
- <4DB84D65.6070906@gmail.com>
On Thu, Apr 28, 2011 at 3:07 AM, A Large Angry SCM <gitzilla@gmail.com> wrote:
Show 5 quoted lines
> > 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.
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.