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" Signed-off-by: Jeff King <peff@xxxxxxxx> --- On Wed, Apr 09, 2008 at 10:57:58AM -0400, Jeff King wrote: > > then i tried git-remote show -a (to list all repositories, etc.) - what > > i didnt figure out was to show all repositories is to do a simple > > "git-remote". I think "git-remote show" should output all repositories, > > or at least indicate it in its help line what to do to get such a list. > > (for us poor sobs forgetting commandline details ;) > > Yes, just showing the remotes would be consistent with what other > commands do (e.g., git-branch, git-tag). I'll post a patch in a minute. And here it is. builtin-remote.c | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/builtin-remote.c b/builtin-remote.c index d77f10a..06d33e5 100644 --- a/builtin-remote.c +++ b/builtin-remote.c @@ -19,6 +19,8 @@ static const char * const builtin_remote_usage[] = { static int verbose; +static int show_all(void); + static inline int postfixcmp(const char *string, const char *postfix) { int len1 = strlen(string), len2 = strlen(postfix); @@ -380,8 +382,11 @@ static int show_or_prune(int argc, const char **argv, int prune) argc = parse_options(argc, argv, options, builtin_remote_usage, 0); - if (argc < 1) + if (argc < 1) { + if (!prune) + return show_all(); usage_with_options(builtin_remote_usage, options); + } memset(&states, 0, sizeof(states)); for (; argc; argc--, argv++) { -- 1.5.5.1.g272c -- 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