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

[BUG] 'git merge --quiet' is not always quiet

From
CMCarl Mäsak <cmasak@gmail.com>
Date
Apr 2, 2015, 12:42 UTC
Message-ID
<CADwUm8do1+2aAqSnwMmViTCwA9jpAZM21DtRP9YiniVtCenFKw@mail.gmail.com>

In the following session, a 'git merge' command shows some output even with the '--quiet' flag supplied.

    ~/tmp $ git init example
    Initialized empty Git repository in /tmp/example/.git/
    ~/tmp $ cd example/
    ~/tmp/example $ git commit --allow-empty -m'initial commit'
    [master (root-commit) a7329b5] initial commit
    ~/tmp/example $ git checkout -b b1
    Switched to a new branch 'b1'
    ~/tmp/example $ git commit --allow-empty -m'commit on branch'
    [b1 d15e5ac] commit on branch
    ~/tmp/example $ git checkout master
    Switched to branch 'master'
    ~/tmp/example $ git merge --quiet --no-ff --no-edit b1
    Already up-to-date!
    ~/tmp/example $
My expectation is that '--quiet' would suppress all output, even this one.

I'm on Git 1.9.1, but I've been informed on IRC that this happens even on latest.

// Carl
Next: Jeff King
Message 1 of 2 in “[BUG] 'git merge --quiet' is not always quiet”
  1. Carl MäsakApr 2, 2015
  2. Jeff KingApr 2, 2015

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.