Re: [BUG] 'git log --quiet' doesn't suppress the output
- From
- James Pickens <jepicken@gmail.com>
- Date
- Feb 7, 2009, 07:18 UTC
- Message-ID
- <885649360902062318n4e51ded0r957f6199ff9afc1a@mail.gmail.com>
- In-Reply-To
- <20090207065602.GA14995@coredump.intra.peff.net>
On Fri, Feb 6, 2009 at 11:56 PM, Jeff King <peff@peff.net> wrote:
Show 15 quoted lines
> On Fri, Feb 06, 2009 at 11:44:59PM -0700, James Pickens wrote: > >> 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. > > OK, that does make sense. > > In this case, though, you should be using the "git rev-list" plumbing > instead of the "git log" porcelain for a script. And "git rev-list" does > support "--quiet", but it doesn't quite do what you want. It silences > the output, but the exit code does not depend on whether or not there > were any commits in range.
Thanks for the tip; I'll just use rev-list and check if it gave any output.
James