>> Once I included the whole email in my reply, but otherwise I deleted it >> all. > Both are bad practice. If you are considerate with the reader's time, this > consideration is typically reprocicated. So it is a good idea to save the > reader time by giving them the precise context they need. This is among a few reasons I don't understand why in 2016 we use mail lists for this kind of stuff. First time I've had to deal with this since the 1990's so I forgot how it works. On Mon, May 16, 2016 at 11:17 AM, Jeff King <peff@xxxxxxxx> wrote: > 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. As I was mentioning GitHub I assumed "Microsoft implementation" would indicate their hosted Git service "Visual Studio Team Services". I really didn't think there was anything else to provide. The feedback lead me to test with Github and with that I verified that when the remote was for Github it worked, but when the remote was VSTS it was not.. and "not working" means not paying attention to "--quiet" setting only with git push, while it does work for other commands such as clone. (though I think I have to re-test with pull.) The problem is not with Powershell (though how it handles seeing output in STDERR is not anything I agree with). I was merely trying to point out that 'git push --quiet' was not working until we realized it was with VSTS. This "ticket" if it exists as such in a maillist can be closed. I think this accurately sums it up: > 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