git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUG] 'git log --quiet' doesn't suppress the output

From
JPJames Pickens <jepicken@gmail.com>
Date
Feb 7, 2009, 06:44 UTC
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
Previous: Jeff KingNext: Jeff King
Message 3 of 5 in “[BUG] 'git log --quiet' doesn't suppress the output”
  1. James PickensFeb 5, 2009
  2. Jeff KingFeb 6, 2009
  3. James PickensFeb 7, 2009
  4. Jeff KingFeb 7, 2009
  5. James PickensFeb 7, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.