On Wednesday 2006 December 13 22:48, Jakub Narebski wrote: > Nice list, although I'd rather add extra output only if command is used > with -v/--verbose (or -V/--verbose) option; if not, then add -q/--quiet > (or -s/--silent) option to be used in scripts. I'm partial to --verbose I'd rather have the scripts requiring "--quiet"; because otherwise it's another switch for a newbie to guess at. However, I don't think that switches is the answer. Output for these porcelain-level commands is not structured enough to be used in scripts anyway (e.g. git-pull), but what it does output is a confusing lump. > solution, as advanced users are not interested in any output; they know > the commands, and want them to be fast. C.f GNU tar: it outputs something > only with -v/--verbose option. tar is doing a considerably less complicated sequence of operations than many of git's commands, so I don't think that's a fair comparison. Also; I don't think "experts" should care about the extra output - I can't imagine that an extra few lines of text is going to slow git down. Further, I think the problem in most cases is that git outputs _too much_. Also, I'm not imagining that "git-add ." would list every file that it added - who is that going to help? It should say "added X files to index" or similar. You surely can't be arguing that that slows down your expert workflow? I believe that a good set of output will be useful to both newbies and experts alike. The idea that experts don't like to know what's going on is simply not true. The idea that newbies want to see every file listed and every operation described is simply not true. Andy -- Dr Andy Parkins, M Eng (hons), MIEE andyparkins@xxxxxxxxx - 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