From: Daniel Tang <danielzgtg.opensource@gmail.com>
To: gitster@pobox.com
Cc: cedricschwyter@bluewin.ch, git@vger.kernel.org
Subject: Re: [PATCH 0/1] Alias 'list'-subcommands to 'ls'
Date: Tue, 27 Jan 2026 12:01:04 -0500 [thread overview]
Message-ID: <3411428.b9nUPlyArG@daniel-desktop3> (raw)
In-Reply-To: <xmqqblh7nqmu.fsf@gitster.c.googlers.com>
> Is there a "git somecmd" that allows "git somecmd ls" form, while
`git fast-import` comes close but isn't really it.
> these "git stash list", "git worktree list" subcommands take "list"
> and not "ls"? If so, this change may make sense, but otherwise, not
> really.
We have a precedent of aliases how `git remote rm` is aliased to
`git remote remove`. Speaking of which, I'd also like an alias from
`git remote mv` to `git remote rename`.
> Since many CLI-tools make use of this alias and many programmers are
> used to it I thought I'd add it to git since I was missing such an alias.
Yes, I run into this once a week. `git-ls-files`, `git-ls-remote`, and
`git ls-tree` misleadingly imply that Git commonly writes "list" as
"ls". I'm accustomed to `npm ls` being accepted, and even `ip link ls`
ignores the extra subcommand. I perceive a command line convention to
alias subcommands to coreutils abbreviations e.g. `git rm`/
`docker container rm`/`docker container cp`.
prev parent reply other threads:[~2026-01-27 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 19:53 [PATCH 0/1] Alias 'list'-subcommands to 'ls' Cedric Schwyter
2020-10-12 19:53 ` [PATCH 1/1] subcommands: alias 'list'-subcommands to 'ls' where applicable docs: update docs with new alias Cedric Schwyter
2020-10-12 20:19 ` [PATCH 0/1] Alias 'list'-subcommands to 'ls' Junio C Hamano
2020-10-12 20:55 ` Cedric Schwyter
2026-01-27 17:01 ` Daniel Tang [this message]
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=3411428.b9nUPlyArG@daniel-desktop3 \
--to=danielzgtg.opensource@gmail.com \
--cc=cedricschwyter@bluewin.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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