On 10/11/2015 18:12, Stefan Beller wrote:
On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton<admin@xxxxxxxxxxxxxx> wrote:
It's recently come to my attention that the "git alias" config functionality
ignores all aliases that would override existing Git commands. This seems
like a bad idea to me.
This ensures that the plumbing commands always work as expected.
As scripts *should* only use plumbing commands, the scripts should
work with high probability despite all the crazy user configuration/aliases.
I just disagree with this. If a user chooses to override their Git
commands, it's their problem. Why should Git care about this? It
should provide the user with the option to do this, and if the user
ruins scripts because of their aliases, it is not Git's problem. What
you are doing is taking away power from users to use git aliases to
their full potential.
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html