Re: git silently ignores aliases of existing commands
- From
- demerphq <demerphq@gmail.com>
- Date
- Jul 18, 2009, 09:30 UTC
- Message-ID
- <9b18b3110907180230p7fb432cdq56bfee794afc669e@mail.gmail.com>
- In-Reply-To
- <4A6176E6.4060708@pobox.com>
2009/7/18 Michael G Schwern <schwern@pobox.com>:
Show 25 quoted lines
> Sean Estabrooks wrote: >> 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. >> >> 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. > > I'm in the "more than enough rope" camp myself, so count that as a -1 fwiw. > > More importantly, what about the warning telling the user that what they did > is not allowed and didn't work?
Yeah it seems reasonable that if its going to be ignored it should not be silently ignored.
Especially given that the silentness effectively means there cant be any new git tools added without possible breakage of installed setups.
cheers, Yves
-- perl -Mre=debug -e "/just|another|perl|hacker/"