Re: [git-users] Highlevel (but simple to implement) commands provided by default for git

From: Jonathan Nieder <jrnieder@gmail.com>
Date: May 29, 2013, 23:43 UTC
Message-ID: <20130529234335.GE28153@google.com>
In-Reply-To: <CALkWK0=5BwterP7ATM1GgFvLUs391w_MW4YrwbnvsbM6Q4_Opg@mail.gmail.com>

Ramkumar Ramachandra wrote:

> Bráulio Bhavamitra wrote:

Show 8 quoted lines

>> 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.

Hope that helps, Jonathan