From: Felipe Contreras Date: Thu, 30 May 2013 15:32:48 GMT Subject: Re: [git-users] Highlevel (but simple to implement) commands provided by default for git Message-ID: In-Reply-To: <20130530145447.GC4884@elie.Belkin> On Thu, May 30, 2013 at 9:54 AM, Jonathan Nieder wrote: > Felipe Contreras wrote: >> On Thu, May 30, 2013 at 12:23 AM, Jonathan Nieder wrote: >>> Felipe Contreras wrote: >>>> On Wed, May 29, 2013 at 6:43 PM, Jonathan Nieder wrote: > >>>>> A bigger problem (in my opinion) with allowing arbitrary changes to >>>>> the meaning of existing commands is that scripts, whether placed in >>>>> .sh files or given as commands to run over IRC, stop working >>>>> altogether. It's nice to have commands like "git log" and "git am" >>>>> mean the same thing no matter what machine I am on. >>>> >>>> Except that's not true: >>> >>> It's not true that my opinion is that a bigger problem than the >>> non-problem Ram mentioned with allowing arbitrary changes to the >>> meaning of existing commands is that scripts stop working reliably? >> >> It's not true what you said: >> >> commands like "git log" and "git am" mean the same thing no matter >> what machine I am on. > > It's not true that it's nice when they do? Yeah, it's nice that the sun is purple. Never-mind the fact that it's not true. The consistency you experience across machines has absolutely nothing to do with Git, since Git can be configured in a way you don't consider nice. So this argument is invalid. Any proposed change to make Git more configurable is not affected by this argument, because Git can *already* be configured in a way that would break your experience, yet it doesn't happen. In other words; it's the policy or your machine users you have to thank for, not Git's code, and changing Git's code is not going to change that policy. Either way this is a straw man, again, nobody is pushing to allow builtins to be overridable. The topic is default *aliases*. -- Felipe Contreras