From: Felipe Contreras Date: Thu, 30 May 2013 03:08:46 GMT Subject: Re: [git-users] Highlevel (but simple to implement) commands provided by default for git Message-ID: In-Reply-To: <20130529234335.GE28153@google.com> On Wed, May 29, 2013 at 6:43 PM, Jonathan Nieder wrote: > Ramkumar Ramachandra wrote: >> Bráulio Bhavamitra wrote: > >>> Agree, these aliased should work as a fallback or as an automatic short >>> version >> >> Making builtins override'able is also a terrible idea. It opens doors >> to potential bugs we don't want to deal with. Simple example: >> >> am = log -1 >> log = am -3 > > That's detectable and could be made to error out, so it's not too bad. > > 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: % git config --global format.pretty oneline Either way, this is a red herring, I don't see anybody pushing for overriding builtins. -- Felipe Contreras