From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, David Aguilar <davvid@gmail.com>
Subject: Re: [PATCH v3] build: add default aliases
Date: Tue, 24 Sep 2013 01:59:21 -0500 [thread overview]
Message-ID: <CAMP44s0RPgVOo4qN-Nb2Mqkemk53gi_pu7Ft25e3gtFciNOEgw@mail.gmail.com> (raw)
In-Reply-To: <20130924064604.GA7257@sigill.intra.peff.net>
On Tue, Sep 24, 2013 at 1:46 AM, Jeff King <peff@peff.net> wrote:
> On Tue, Sep 24, 2013 at 01:41:19AM -0500, Felipe Contreras wrote:
>
>> > People who have different aliases for
>> > the same terms are unaffected on existing boxes, but slightly hindered
>> > on new boxes as the aliases do something else.
>>
>> Less hindered than in the current situation.
>
> I do not agree, but I've already explained my reasoning. I think we
> must agree to disagree on this.
>
>> cvs ci = cvs commit
>> cvs co = cvs checkout
>>
>> svn ci = svn commit
>> svn co = svn checkout
>>
>> hg ci = hg commit
>> hg co = hg checkout
>>
>> And somehow you think this is not natural and sensible?
>>
>> git ci = git commit
>> git co = git checkout
>>
>> I think it's as clear as day.
>
> If it is natural, sensible, and as clear as day, then why do people
> alias the commands to something besides what you show?
For the same reason people would do alias.commit='commit -a' if it was possible.
[1] http://article.gmane.org/gmane.comp.version-control.git/147517
--
Felipe Contreras
next prev parent reply other threads:[~2013-09-24 6:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 19:20 [PATCH v3] build: add default aliases Felipe Contreras
2013-09-24 4:53 ` Jeff King
2013-09-24 5:32 ` Felipe Contreras
2013-09-24 5:37 ` Jeff King
2013-09-24 5:49 ` Felipe Contreras
2013-09-24 6:18 ` Jeff King
2013-09-24 6:41 ` Felipe Contreras
2013-09-24 6:46 ` Jeff King
2013-09-24 6:59 ` Felipe Contreras [this message]
2013-09-24 18:39 ` Jonathan Nieder
2013-09-24 19:30 ` John Szakmeister
2013-09-28 22:41 ` Felipe Contreras
2013-09-29 3:18 ` Michael Haggerty
2013-09-29 3:37 ` Felipe Contreras
2013-09-30 19:33 ` Jonathan Nieder
2013-10-01 1:12 ` Duy Nguyen
2013-10-15 22:34 ` Junio C Hamano
2013-10-16 3:43 ` Felipe Contreras
2013-10-17 19:51 ` Junio C Hamano
2013-10-17 21:34 ` Felipe Contreras
2013-09-24 9:19 ` John Szakmeister
2013-09-24 10:25 ` Felipe Contreras
2013-09-24 11:06 ` John Szakmeister
2013-09-24 14:35 ` Felipe Contreras
2013-09-25 13:33 ` John Szakmeister
2013-09-25 14:29 ` Felipe Contreras
2013-09-25 14:55 ` Matthieu Moy
2013-09-25 15:08 ` Felipe Contreras
2013-09-25 15:13 ` Matthieu Moy
2013-09-25 15:16 ` Felipe Contreras
2013-09-25 16:05 ` Matthieu Moy
2013-09-25 16:36 ` Felipe Contreras
2013-09-24 15:21 ` SZEDER Gábor
2013-09-24 15:33 ` [PATCH v4] " 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=CAMP44s0RPgVOo4qN-Nb2Mqkemk53gi_pu7Ft25e3gtFciNOEgw@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).