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

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

From
Jeff King <peff@peff.net>
Date
Feb 6, 2009, 19:11 UTC
Message-ID
<20090206191146.GC19494@coredump.intra.peff.net>
In-Reply-To
<885649360902041819k4a168407wc57017e6a1c7d00a@mail.gmail.com>
On Wed, Feb 04, 2009 at 07:19:28PM -0700, James Pickens wrote:
> The --quiet switch to 'git log' doesn't suppress the output.  It only
> does the same as --exit-code.

It suppresses the diff output (which is why it supports --quiet at all: it is a diff option). So

  git log -p --quiet
looks just like
  git log
making it largely pointless.

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?

-Peff
Previous: James PickensNext: James Pickens
Message 2 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.