git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Chris B <chris.blaszczynski@gmail.com>, git@vger.kernel.org
Subject: Re: git push --quiet option does not seem to work
Date: Mon, 16 May 2016 11:17:21 -0400	[thread overview]
Message-ID: <20160516151721.GA8678@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1605161700360.3303@virtualbox>

On Mon, May 16, 2016 at 05:04:34PM +0200, Johannes Schindelin wrote:

> > Anyway, it is not a Powershell thing. I tested on another repo on
> > GitHub and it worked as expected. So I guess indeed the problem lies
> > with Microsoft's implementation.
> 
> This is *really* unclear.
> 
> What "Microsoft's implementation"??? Do you refer to VSTS, or do you refer
> to Git for Windows, or PowerShell?
> 
> Please. To make it really simple for everybody involved, try to repeat as
> closely as possible the same push from PowerShell, Git CMD and Git Bash.
> We want to compare oranges to oranges.

I don't think there is much to debug there. According to

  http://superuser.com/questions/213848/using-powershell-call-native-command-line-app-and-capture-stderr/462362#462362

and other sources, it looks like PowerShell is very picky about calling
programs which produce any output on stderr, and may in an error object.
So I think both Powershell and Git are working as advertised, it's just
that their behaviors are incompatible.

The "bug" is that the server is asking the client to write non-error
output to stderr, even though the client should have asked the server to
be quiet (though it would not hurt to check that it is doing so by
looking at the output of GIT_TRACE_PACKET).

-Peff

  reply	other threads:[~2016-05-16 15:17 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
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 [this message]
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=20160516151721.GA8678@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --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).