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

From: Jeff King <peff@peff.net>
Date: May 16, 2016, 13:37 UTC
Message-ID: <20160516133731.GA6903@sigill.intra.peff.net>
In-Reply-To: <alpine.DEB.2.20.1605161526510.3303@virtualbox>

On Mon, May 16, 2016 at 03:28:30PM +0200, Johannes Schindelin wrote:

Show 17 quoted lines

> > PS H:\test-ps\myrepo> git push --quiet
> > git : remote:
> > At line:1 char:1
> > + git push --quiet
> > + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >     + CategoryInfo          : NotSpecified: (remote: :String) [],
> > RemoteException
> >     + FullyQualifiedErrorId : NativeCommandError
> > 
> > remote: Analyzing objects... (3/3) (119 ms)
> > remote: Storing packfile... done (113 ms)
> > remote: Storing index... done (29 ms)
> 
> So it actually works, eh?
> 
> Could you please verify that this is a PowerShell-only problem by
> performing a similar push in Git CMD and in Git Bash?

I don't know much about PowerShell, but presumably it is responsible for the first few lines.

But there is something else going on, too, which is those "remote:" lines. Those are being relayed from the server by the git client. I don't think it would be correct for the client to suppress them, even with "--quiet", because the client side has no idea if they are progress junk or critical error messages.

The client _does_ pass along the "quiet" flag to the server via the git protocol, so it should be the server's responsibility to drop progress output when it is present. The server side here is clearly not stock git, from the content of those progress messages (some googling shows it looks like whatever visualstudio.com is running, but I don't know what that is). So either the server implementation doesn't support the "quiet" protocol extension, or it is ignoring it. It might be worth filing a bug with them.

-Peff