Re: RFC: a plugin architecture for git extensions?

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 27, 2011, 05:17 UTC
Message-ID: <7vsjt49stq.fsf@alter.siamese.dyndns.org>
In-Reply-To: <BANLkTinFX24gTR-0PK8Tyi5aOf8rnLk6Cg@mail.gmail.com>

Jon Seymour <jon.seymour@gmail.com> writes:

>> So if you have /home/js/bin on your $PATH, you can install your "git-work"
>> script as /home/js/bin/git-work, and that should be sufficient.
>
> Yep, that's a start, but does not a a complete plugin architecture make :-)

Please explain yourself.

Message 6 of 105 in “RFC: a plugin architecture for git extensions?”

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.