From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
git@vger.kernel.org, David Aguilar <davvid@gmail.com>
Subject: Re: [PATCH v3] build: add default aliases
Date: Tue, 15 Oct 2013 22:43:42 -0500 [thread overview]
Message-ID: <525e0b6e25aeb_81a151de7495@nysa.notmuch> (raw)
In-Reply-To: <xmqqy55ub1ud.fsf@gitster.dls.corp.google.com>
Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > It seems[1] that some
> > people define "ci" as "commit -a", and some people define "st" as
> > "status -s" or even "status -sb".
>
> These option variants aside.
>
> Just like thinking that committing must be the same as publishing,
> it is a cvs/svn induced braindamage to think that "checking in" must
> be the same as "committing". The former is a sign of not
> understanding the "distributed", the latter "the index".
>
> In a world with both check-in and commit as two words usable to
> denote possibly different concepts, it may make sense to say "you
> check-in the current status of the working tree files into the
> index, in order to make commits out of it later".
Yet a wide amount of users do use 'ci' to mean 'commit', so basically they are
just wrong. So you are saying they are just ignorant.
Personally I don't care if it's 'ci', or 'co', or 'cm', or 'ct'. I just
want/need a shortcut, then I can train my fingers to type that.
If you have a better alias than 'ci', then by all means, throw away your
suggestion.
Now, if you are commenting on the aliases, that would mean you are not against
the idea of aliaes per se, but more about values of those aliases. So if we
agreed on the right values, you would welcome this patch.
Is that correct?
--
Felipe Contreras
next prev parent reply other threads:[~2013-10-16 3:58 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525e0b6e25aeb_81a151de7495@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).