From: Sitaram Chamarty <sitaramc@gmail.com>
To: Jeremy Morton <admin@game-point.net>
Cc: Stefan Beller <sbeller@google.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Allow git alias to override existing Git commands
Date: Wed, 11 Nov 2015 15:21:27 +0530 [thread overview]
Message-ID: <56430F9F.7060900@gmail.com> (raw)
In-Reply-To: <56430A27.2030604@game-point.net>
On 11/11/15 14:58, Jeremy Morton wrote:
> On 11/11/2015 04:48, Sitaram Chamarty wrote:
>> 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!)
>
> We're not talking about "normal users" here, that's what Google Chrome
> is for. We're talking about Git users using the commandline client.
> They ought to know what they're doing and if they don't, they're
> screwed anyway because there are quite a few gotchas with Git.
I can only repeat what I said before: it's not all black and white.
Reducing the opportunity to make mistakes is useful for everyone, even
expetrs. Especially stuff that you may have setup aeons ago and hits
you only aeons later when something (supposedly unrelated) somewhere
else changes and you didn't remember and you tear your hair out.
It happens to everyone. The only experts I know who have never torn
their hair out over something silly they forgot (could be anything) are
the ones who were already bald :)
next prev parent reply other threads:[~2015-11-11 9:51 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
2015-11-11 9:28 ` Jeremy Morton
2015-11-11 9:51 ` Sitaram Chamarty [this message]
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=56430F9F.7060900@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).