From: James Pickens <jepicken@gmail.com>
Date: Sat, 07 Feb 2009 06:44:59 GMT
Subject: Re: [BUG] 'git log --quiet' doesn't suppress the output
Message-ID: <885649360902062244v715a61b7nf32003c97cc4f707@mail.gmail.com>
In-Reply-To: <20090206191146.GC19494@coredump.intra.peff.net>

On Fri, Feb 6, 2009 at 12:11 PM, Jeff King <peff@peff.net> wrote:
> It would probably be trivial to for "git log" to see that the quiet
> switch was given and silence the commit output. But I am having trouble
> envisioning exactly what that would be useful for (except for being a
> slower version of "cat /dev/null"). Care to elaborate?

I was writing a script, and looking for a way to figure out
whether there were any commits in origin/master that aren't in
master (i.e., whether I need to pull before I can push), and 'git
log --quiet origin/master..master' was the first thing I thought
of.

James