git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Chris B <chris.blaszczynski@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git push --quiet option does not seem to work
Date: Fri, 13 May 2016 18:33:37 -0400	[thread overview]
Message-ID: <20160513223336.GA18287@sigill.intra.peff.net> (raw)
In-Reply-To: <CADKp0pwHKvfSDG_-4p5tUn0_QiUGKzmRj5RwphfA8sZ_7CVHqw@mail.gmail.com>

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

  reply	other threads:[~2016-05-13 22:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 21:21 git push --quiet option does not seem to work Chris B
2016-05-13 22:33 ` Jeff King [this message]
2016-05-15 20:29   ` Chris B
2016-05-15 20:34     ` Chris B
2016-05-15 21:23     ` Jeff King
2016-05-16  0:51       ` Chris B
2016-05-16  0:58         ` Jeff King
2016-05-16 13:13           ` Chris B
2016-05-16 13:28             ` Johannes Schindelin
2016-05-16 13:37               ` Jeff King
2016-05-16 14:32                 ` Chris B
2016-05-16 15:04                   ` Johannes Schindelin
2016-05-16 15:17                     ` Jeff King
2016-05-17  0:06                       ` Chris B

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160513223336.GA18287@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=chris.blaszczynski@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).