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 17:14:39 -0500	[thread overview]
Message-ID: <60df8fcf71d11_28bb20873@natae.notmuch> (raw)
In-Reply-To: <cb40e459-7862-b917-b4bb-7bd6f929adef@mfriebe.de>

martin wrote:
> On 02/07/2021 23:12, Felipe Contreras wrote:
> > 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.
> 
> But it is not that different between git and svn/cvs
> 
> svn/cvs both store/restore from the repository. That happens to be on 
> the server.
> git  store/restore from the repository. That happens to be local. (the 
> remote is optional in git)

Fair point.

However, I don't think git actually checks out anything. If you see the
English definition [1] the CVS checkout can be thought of as checking
out a book from the library; the item you check out is not part of the
repository afterwards. Git doesn't do that.

Either way we could leave the 'co' alias pending to see what happens
with switch/restore, but my guess is that as time goes by 'checkout'
will be used less and less.

> That, said, it is ok to break with the old patterns. Otherwise 
> innovation can't happen.
> But, plenty of users have old habits, and those die hard.
> If the new aliases should help people, then those used to other meanings 
> of the same alias may not think of it as that much help.

Right, but not all users have old habits. Some were born after
Subversion was created. An important decision such as default aliases
should look into the future, not the past.

> Also, git has plenty more commands than other vcs. Even if not all of 
> them will be aliased, people will expect different sub sets of them in 
> the list of those with alias.
> Maybe 3 letter aliases will be less controversial

I don't think so. In my opinion the list of default aliases should be
small, and for that two characters is fine.

Cheers.

[1] https://www.merriam-webster.com/dictionary/checkout

-- 
Felipe Contreras

  reply	other threads:[~2021-07-02 22:14 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
2021-07-02 21:31               ` martin
2021-07-02 22:14                 ` Felipe Contreras [this message]
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=60df8fcf71d11_28bb20873@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).