git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: martin <test2@mfriebe.de>,
	Felipe Contreras <felipe.contreras@gmail.com>,
	Andreas Schwab <schwab@linux-m68k.org>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH 5/5] config: add default aliases
Date: Fri, 02 Jul 2021 16:12:25 -0500	[thread overview]
Message-ID: <60df813938303_28bb208c8@natae.notmuch> (raw)
In-Reply-To: <3e82a574-fdcc-08b8-8fb5-1ff15f8ae564@mfriebe.de>

martin wrote:
> On 02/07/2021 12:54, Felipe Contreras wrote:
> > martin wrote:
> >> IMHO it would be good to (partly) follow other vcs, and have
> >> commit = ci
> > I'm fine with leaving co out of the default aliases if it's deemed "too
> > controversial".
> >
> > But ci doesn't make sense. ci comes from "check in" which has no
> > similitude in git.
> svn uses it for "commit".
> It can be seen as CommIt.

I know, but it comes from CVS.

In both CVS and Subversion "commit" pushes a commit, so it can be seen
as the opposite of "checkout", which pulls a commit.

That's not the case in git.

> But of course other letters can be picked. I don't see an advantage in 
> it though.

The advantage is that it's straightforward: co -> commit.

> > I don't think it's a good idea to leave "git checkout" without an alias
> > (it's perhaps the second or third most used command), but at least some
> > aliases are better than no aliases.
> Well, that goes back to a bigger question. And from the brief time I 
> have been on this mail
> list, it appears to me there is a divide into 2 groups.

I'm on neither of those camps.

> If checkout is really meant to give way to switch/restore then it needs 
> no further
> advertising. And then the current usage statistics are a relict from the 
> before switch/restore time.

This is what I think eventually should happen, but we are not there yet.

If checkout were to disappear today, I wouldn't be able to do a lot of
things. switch/restore are not ready yet.

> If on the other hand checkout is not just to be kept for backward 
> compatibility, but should
> always remain an equal alternative to switch/restore (i.e. it should 
> still be taught to new
> user in 20 years) then it wants to have a default alias.

Why? Not all commands need an alias, only the most widely used. If
switch/restore can be used for 99% of use cases (not the case today),
then there's no need for checkout to have a default alias.

Of course if somebody wants to keep using checkout instead of
switch/restore, they can add an alias themselves.


I'm on the camp of "let's see".

-- 
Felipe Contreras

  parent reply	other threads:[~2021-07-02 21:12 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 10:05 [PATCH 0/5] Default aliases Felipe Contreras
2021-07-02 10:05 ` [PATCH 1/5] test: add missing whitespaces Felipe Contreras
2021-07-02 10:05 ` [PATCH 2/5] config: trivial style fix Felipe Contreras
2021-07-02 10:05 ` [PATCH 3/5] config: trivial struct initialization cleanup Felipe Contreras
2021-07-02 10:05 ` [PATCH 4/5] config: initialize origin_type correctly Felipe Contreras
2021-07-02 10:05 ` [PATCH 5/5] config: add default aliases Felipe Contreras
2021-07-02 10:10   ` Andreas Schwab
2021-07-02 10:17     ` Felipe Contreras
2021-07-02 10:31       ` Andreas Schwab
2021-07-02 10:46         ` Felipe Contreras
2021-07-02 10:54           ` Andreas Schwab
2021-07-02 10:44       ` martin
2021-07-02 10:54         ` Felipe Contreras
2021-07-02 11:15           ` martin
2021-07-02 13:26             ` Randall S. Becker
2021-07-02 13:41               ` Ævar Arnfjörð Bjarmason
2021-07-02 14:15                 ` Randall S. Becker
2021-07-02 14:43                   ` martin
2021-07-02 20:44                     ` Felipe Contreras
2021-07-02 22:03                     ` Randall S. Becker
2021-07-02 22:32                       ` Felipe Contreras
2021-07-02 15:39               ` Junio C Hamano
2021-07-02 20:41                 ` Felipe Contreras
2021-07-02 21:02               ` Felipe Contreras
2021-07-02 21:40                 ` martin
2021-07-02 22:16                   ` Felipe Contreras
2021-07-02 22:00                 ` Randall S. Becker
2021-07-02 22:31                   ` Felipe Contreras
2021-07-02 21:12             ` Felipe Contreras [this message]
2021-07-02 21:31               ` martin
2021-07-02 22:14                 ` Felipe Contreras
2021-07-02 11:32   ` Ævar Arnfjörð Bjarmason
2021-07-02 21:58     ` Felipe Contreras
2021-07-02 22:38       ` martin
2021-07-02 23:48         ` Felipe Contreras
2021-07-05 14:02         ` Randall S. Becker
2021-07-06 15:27           ` Randall S. Becker
2021-07-06 21:59           ` Felipe Contreras
2021-07-10 15:30           ` Philip Oakley
2021-07-03 10:50   ` Jeff King
2021-07-06 21:54     ` 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=60df813938303_28bb208c8@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=schwab@linux-m68k.org \
    --cc=test2@mfriebe.de \
    /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).