* Jeff King <peff@xxxxxxxx> wrote:
> Many other commands use the "no arguments" form to show a
> list (e.g., git-branch, git-tag). While we did show all
> remotes for just "git remote", we displayed a usage error
> for "git remote show" with no arguments. This is
> counterintuitive, since by giving it _more_ information, we
> get _less_ result.
>
> The usage model can now be thought of as:
>
> - "git remote show <remote>": show a remote
> - "git remote show": show all remotes
> - "git remote": assume "show"; i.e., shorthand for "git remote show"
btw., another suggestion: because i use 'git-remote show' rather
frequently, i recently typoed "git-bisect show" and then realized that
it was "git-bisect visualize". Shouldnt there be a "git-bisect show"
alias?
I think using 'show' for all such 'display state' things would be rather
intuitive, if it was applied consistently all across the board.
('visualize' could still remain indefinitely, for compatibility - and
'git-bisect log' would still do the log of the bisection decisions that
were entered.)
Or is there some purpose behind this deviation that i missed?
Ingo
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
