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 -- 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