On Fri, Aug 15, 2014 at 2:56 AM, Jeff King <peff@xxxxxxxx> wrote: > I think this is a fine fix for this specific problem, and we should > apply it. But I do wonder if it would be simpler in the long run to > treat verbosity as a global option, and pass it around via a GIT_QUIET > (or GIT_VERBOSITY) environment variable. > > I would not be surprised at all to find that there are other cases where > sub-programs do not respect the parent verbosity (I know we have had > problems with progress reporting flags carried over the transport > interface in the past, but I think we fixed all of those). I don't see any easy way to make everybody aware of $GIT_QUIET. But the idea is nice. -- Duy -- 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