From: Sitaram Chamarty <sitaramc@gmail.com>
To: Jeremy Morton <admin@game-point.net>, Stefan Beller <sbeller@google.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Allow git alias to override existing Git commands
Date: Wed, 11 Nov 2015 10:18:58 +0530 [thread overview]
Message-ID: <5642C8BA.8030003@gmail.com> (raw)
In-Reply-To: <56424DDE.2030808@game-point.net>
On 11/11/15 01:34, Jeremy Morton wrote:
> On 10/11/2015 18:12, Stefan Beller wrote:
>> On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton<admin@game-point.net> 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.
A lot of things in Unix do follow that "give you rope to hang yourself"
philosophy. I used to (and to *some* extent still do) think like that,
but some years of supporting normal users trying to do stuff has taught
me it's not always that simple.
I can easily see someone blogging some cool way to do something, and a
less savvy user uses that in his gitconfig, and gets burned later
(possibly much later, enough that he does not easily make the
connection!)
So for the record, I am definitely against this kind of change.
But if I were in your place, and really *needed* this, here's what I
would do:
#!/bin/bash
# this file is named 'git' and placed in a directory that is earlier in $PATH
# than the real 'git' binary (typically $HOME/bin). This allows you to
# override git sub-commands by adding stuff like this to your ~/.gitconfig
# (notice the "o-" prefix):
#
# [alias]
# o-clone = clone --recursive
GIT=/bin/git # the real 'git' binary
cmd="$1"
shift
if $GIT config --get alias.o-$cmd >/dev/null
then
$GIT o-$cmd "$@"
else
$GIT $cmd "$@"
fi
next prev parent reply other threads:[~2015-11-11 4:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 16:31 Allow git alias to override existing Git commands Jeremy Morton
2015-11-10 18:12 ` Stefan Beller
2015-11-10 20:04 ` Jeremy Morton
2015-11-10 20:22 ` Stefan Beller
2015-11-11 4:48 ` Sitaram Chamarty [this message]
2015-11-11 9:28 ` Jeremy Morton
2015-11-11 9:51 ` Sitaram Chamarty
2015-11-11 10:12 ` Jeremy Morton
2015-11-11 10:45 ` Sitaram Chamarty
2015-11-11 17:42 ` Stefan Beller
2015-11-10 21:57 ` Jens Lehmann
2015-11-10 22:49 ` Stefan Beller
2015-11-11 19:44 ` Jens Lehmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5642C8BA.8030003@gmail.com \
--to=sitaramc@gmail.com \
--cc=admin@game-point.net \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).