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

Re: git push --quiet option does not seem to work

From
CBChris B <chris.blaszczynski@gmail.com>
Date
May 15, 2016, 20:29 UTC
Message-ID
<CADKp0pw5FFDVvPz0CcjOTYteQ9jFn2jBZwaX6_n8r3UQRGcGdQ@mail.gmail.com>
In-Reply-To
<20160513223336.GA18287@sigill.intra.peff.net>

Try it by making some changes to files and committing them, and then push. It works fine for me when there is nothing to actually push, but not so when there are commits to push.

It always outputs the progress to STDERR even when I add --quiet.
On Fri, May 13, 2016 at 6:33 PM, Jeff King <peff@peff.net> wrote:
Show 36 quoted lines
> On Fri, May 13, 2016 at 05:21:30PM -0400, Chris B wrote:
>
>> Hi I am using 2.8.2.windows.1 and writing Powershell scripts doing
>> some Git stuff.
>>
>> I have to use the --quiet option for git because it constantly outputs
>> progress to stderr.
>>
>> However, it seems that --quiet does not actually work in git push. The
>> output still goes to stderr.
>> When there are changes committed to push it always outputs something
>> to stderr. If there is nothing to push, then it actually is silent.
>
> Can you be more specific? It seems to work for me:
>
>   $ rm -rf dst.git &&
>     git init --bare -q dst.git &&
>     git push dst.git
>   Counting objects: 6, done.
>   Delta compression using up to 8 threads.
>   Compressing objects: 100% (3/3), done.
>   Writing objects: 100% (6/6), 441 bytes | 0 bytes/s, done.
>   Total 6 (delta 0), reused 0 (delta 0)
>   To dst.git
>    * [new branch]      master -> master
>
>   $ rm -rf dst.git &&
>     git init --bare -q dst.git &&
>     git push -q dst.git
>   [no output]
>
> Are you seeing progress reporting, the status table, or something else?
> Are you using a particular protocol that might invoke a git-remote-*
> helper that doesn't respect the quiet flag?
>
> -Peff
Previous: Jeff KingNext: Chris B
Message 3 of 14 in “git push --quiet option does not seem to work”
  1. Chris BMay 13, 2016
  2. Jeff KingMay 13, 2016
  3. Chris BMay 15, 2016
  4. Chris BMay 15, 2016
  5. Jeff KingMay 15, 2016
  6. Chris BMay 16, 2016
  7. Jeff KingMay 16, 2016
  8. Chris BMay 16, 2016
  9. Johannes SchindelinMay 16, 2016
  10. Jeff KingMay 16, 2016
  11. Chris BMay 16, 2016
  12. Johannes SchindelinMay 16, 2016
  13. Jeff KingMay 16, 2016
  14. Chris BMay 17, 2016

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.