From: James Pickens <jepicken@gmail.com>
To: Git ML <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: [BUG] 'git log --quiet' doesn't suppress the output
Date: Fri, 6 Feb 2009 23:44:59 -0700 [thread overview]
Message-ID: <885649360902062244v715a61b7nf32003c97cc4f707@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2009-02-07 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 2:19 [BUG] 'git log --quiet' doesn't suppress the output James Pickens
2009-02-06 19:11 ` Jeff King
2009-02-07 6:44 ` James Pickens [this message]
2009-02-07 6:56 ` Jeff King
2009-02-07 7:18 ` James Pickens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=885649360902062244v715a61b7nf32003c97cc4f707@mail.gmail.com \
--to=jepicken@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).