git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
CBChris B <chris.blaszczynski@gmail.com>
Date
May 17, 2016, 00:06 UTC
Message-ID
<CADKp0px_RzPwwyFVQ6oNE6dn1QNtVUjJ9zCUSgfSn6mdkOrgfQ@mail.gmail.com>
In-Reply-To
<20160516151721.GA8678@sigill.intra.peff.net>
>> 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@peff.net> wrote:
Show 14 quoted lines
> 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:
Show 6 quoted lines
> 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
Previous: Jeff King
Message 14 of 14 in “git push --quiet option does not seem to work”
  1. Chris BMay 13, 2016
  2. Jeff KingMay 13, 2016
  3. Chris BMay 15, 2016
  4. Chris BMay 15, 2016
  5. Jeff KingMay 15, 2016
  6. Chris BMay 16, 2016
  7. Jeff KingMay 16, 2016
  8. Chris BMay 16, 2016
  9. Johannes SchindelinMay 16, 2016
  10. Jeff KingMay 16, 2016
  11. Chris BMay 16, 2016
  12. Johannes SchindelinMay 16, 2016
  13. Jeff KingMay 16, 2016
  14. Chris BMay 17, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.