Re: Improving the git remote command

From: Philippe Vaucher <philippe.vaucher@gmail.com>
Date: Aug 26, 2014, 16:19 UTC
Message-ID: <CAGK7Mr7BPvV6oO_t4x_1m9sDtWBgPWUqDq+3kZx6rVYAhY+wqA@mail.gmail.com>
In-Reply-To: <20140826124027.GE29180@peff.net>

Show 6 quoted lines

> Perhaps "-v" should have been the default all along.  I do not use "git
> remote" myself, so I don't know if "-v" is what most people use. But
> changing the output of "git remote" now is probably a bad thing (I
> expect some people may depend on parsing it to get the list of remotes;
> they should probably use the git-config plumbing to do the same thing,
> but it's actually rather tricky to do it that way).

Just to be clear, the proposal is not about changing the output of "git remote".

Anyway, it got me curious about other git commands reguarding "list", and I was very surprised because I couldn't find another one. I mean "git remote" actually behaves like "git branch" and "git tag". I have no clue why I expect "list" to work with "git remote".

It's probably because "git branch" and "git tag" expect a name, and there "list" can only be expressed by "no name" or with some flags. On the other hand, "git remote" expects a subcommand (add, delete, etc) and there what logically maps to "list" is the subcommand "list", "no name" being more expected to produce a list of the subcommands.

Philippe