Re: git silently ignores aliases of existing commands

From: Sean Estabrooks <seanlkml@sympatico.ca>
Date: Jul 18, 2009, 02:01 UTC
Message-ID: <BLU0-SMTP9743008F68C14C8226D07BAE1F0@phx.gbl>
In-Reply-To: <4A611CE1.3080709@pobox.com>

On Fri, 17 Jul 2009 17:52:49 -0700 Michael G Schwern <schwern@pobox.com> wrote:

[...]

> It would be nice if git used the alias *before* the installed command.  This
> lets me fix/change default behaviors without having to come up with a new
> command.  (Another handy example:  blame = blame -w)  It doesn't do anything
> useful right now anyway.

Hi Michael,

This has been discussed a few times on the list already. Here is one such discussion:

http://thread.gmane.org/gmane.comp.version-control.git/112487/focus=112493

You'll see that it was decided that Git would not allow commands to be overridden so that you could always be sure what a given command would do when you sit down at any installation. This is especially important for scripting but can also be a problem for everyday usage. You'll just have to choose a new command name for the alternate default you want.

[...]

> PS  I couldn't find anything obvious about where to send bug reports / feature
> requests in the git man page, just "general upbringing" pointing here.  It
> would be helpful if it was a bit more clear.  None of "bug", "report" or
> "issue" pointed at anything relevant.

This list is the appropriate place for any of the issues you enumerate.

Cheers, Sean