Re: Improving the git remote command

> ... But we are left with three options:
>
>   1. Add "git remote list" with verbose output. This is bad because it
>      differs gratuitously from "git remote".
>
>   2. Add "git remote list" with non-verbose output. This is good because
>      it means "git remote" is just a shortcut for "git remote list",
>      which is consistent with other parts of git. But it is potentially
>      bad if "-v" is a better output format.
>
>   3. Add "git remote list" with verbose output, and tweak "git remote"
>      to match. This is bad because it breaks backwards compatibility.
>
> The proposal is for (1). I think we agree that (3) is out. The question
> is whether (1) or (2) is the least bad.

> Yeah. Branch and tag need dashed subcommands because otherwise it is
> ambiguous with creating tag called "list", functionality that existed
> before "--list" was added. Git-remote was defined with subcommands from
> day one, so it can get away with it. Git-stash is sort of in the
> category as git-remote there, except that "save" can actually take an
> argument. So to provide it you can't say "git stash foobar", but instead
> have to say "git stash save foobar" (it actually used to allow the
> former, but you can imagine the annoyance when you typo "git stash
> lsit").