Re: [PATCH 5/5] config: add default aliases

From: martin <test2@mfriebe.de>
Date: Jul 2, 2021, 11:15 UTC
Message-ID: <3e82a574-fdcc-08b8-8fb5-1ff15f8ae564@mfriebe.de>
In-Reply-To: <60def07e686c7_7442083a@natae.notmuch>

On 02/07/2021 12:54, Felipe Contreras wrote:

Show 8 quoted lines

> 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.

But of course other letters can be picked. I don't see an advantage in it though. Like CoMmit cm ? or CommiT ct ? None of them seems any better to me.

> 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.

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.

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.