From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Ramkumar Ramachandra" <artagnon@gmail.com>,
"Bráulio Bhavamitra" <brauliobo@gmail.com>,
git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: [git-users] Highlevel (but simple to implement) commands provided by default for git
Date: Wed, 29 May 2013 22:08:46 -0500 [thread overview]
Message-ID: <CAMP44s3807Dk0SOZcBbaOKTLj5k36bW0SA9F5ZBY2MwS1Nnxiw@mail.gmail.com> (raw)
In-Reply-To: <20130529234335.GE28153@google.com>
On Wed, May 29, 2013 at 6:43 PM, Jonathan Nieder <jrnieder@gmail.com> 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
next prev parent reply other threads:[~2013-05-30 3:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f611150e-a12a-47f6-97f0-8aaff3045338@googlegroups.com>
[not found] ` <f611150e-a12a-47f6-97f0-8aaff3045338-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2013-05-29 18:05 ` Highlevel (but simple to implement) commands provided by default for git Bráulio Bhavamitra
2013-05-29 18:11 ` Fwd: [git-users] " Bráulio Bhavamitra
2013-05-29 18:26 ` Ramkumar Ramachandra
2013-05-29 19:50 ` Felipe Contreras
2013-05-29 20:00 ` Ramkumar Ramachandra
2013-05-30 2:48 ` Felipe Contreras
2013-05-29 20:07 ` Junio C Hamano
2013-05-29 20:19 ` Ramkumar Ramachandra
2013-05-29 21:15 ` Junio C Hamano
2013-05-29 21:26 ` Ramkumar Ramachandra
2013-06-02 19:20 ` Junio C Hamano
2013-06-03 23:22 ` Duy Nguyen
2013-05-29 18:58 ` Fwd: " Junio C Hamano
2013-05-29 19:39 ` Felipe Contreras
2013-05-29 20:27 ` Ramkumar Ramachandra
[not found] ` <CAJri6_uScqjovt5eK9f9+Z4ehtsdYQNuiEX1MERiDBEJWueAXg@mail.gmail.com>
2013-05-29 21:32 ` Ramkumar Ramachandra
2013-05-29 23:43 ` Jonathan Nieder
2013-05-30 3:08 ` Felipe Contreras [this message]
2013-05-30 5:23 ` Jonathan Nieder
2013-05-30 5:28 ` Felipe Contreras
2013-05-30 14:54 ` Jonathan Nieder
2013-05-30 15:32 ` Felipe Contreras
2013-05-30 7:30 ` Ramkumar Ramachandra
2013-05-30 3:04 ` Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMP44s3807Dk0SOZcBbaOKTLj5k36bW0SA9F5ZBY2MwS1Nnxiw@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=artagnon@gmail.com \
--cc=brauliobo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).