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@xxxxxxxx> wrote: > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html