Subject: Re: RFC: a plugin architecture for git extensions?

From: David Aguilar <[email-masked]>
Date: Sat, 14 May 2011 05:51:36 -0700

On Mon, May 09, 2011 at 01:36:16PM +0900, Miles Bader wrote:
> Junio C Hamano <[email-masked]> writes:
> > Do you or do you not run "apt-get install git-superadd"?
> >
> > One possible answer may be to run "apt-get install git-superadd", and then
> > the users who want "git add" to behave in a new way to opt-in to use the
> > "plug-in".  I think that is what Jon is getting at.
> 
> If aliases could override built-in command names, it'd be easy enough
> ("alias add=superadd") ... [with some feature to allow suppressing the
> alias to prevent recursion, e.g. an environment variable or something.]

I always thought this restriction was a good thing.

The usability argument usually goes that it's generally
bad for "git frotz" somewhere to behave different from
"git frotz" somewhere else.

Keeping this "limitation" is good for the sake of consistency.

This topic is orthogonal to the plugin rfc, though.
-- 
					David