Git development
 help / color / mirror / Atom feed
From: "Scott R. Chamberlain" <srchamberlain@impromed.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: Can't get git to stop outputting to StdErr
Date: Mon, 19 Dec 2016 14:56:35 +0000	[thread overview]
Message-ID: <77ad6aeef9a245f3adeab3751e7e94eb@ES5.impromed.com> (raw)
In-Reply-To: xmqq7f8syyhg.fsf@gitster.mtv.corp.google.com

Microsoft fixed their git repo implementation to no longer cause this problem.

https://connect.microsoft.com/VisualStudio/feedback/details/3109654/git-host-on-visualstudio-com-does-not-respect-the-q-flag-for-pushes

Scott Chamberlain
Software Engineer 
ImproMed, LLC
(800) 925-7171
www.impromed.com

-----Original Message-----
From: Scott R. Chamberlain 
Sent: Friday, October 28, 2016 4:09 PM
To: 'Junio C Hamano' <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: RE: Can't get git to stop outputting to StdErr

This is talking to a visualstudio.com git repo. I will file a bug with them.

Scott Chamberlain
Software Engineer 
ImproMed, LLC
(800) 925-7171
www.impromed.com


-----Original Message-----
From: Junio C Hamano [mailto:gitster@pobox.com] 
Sent: Friday, October 28, 2016 4:07 PM
To: Scott R. Chamberlain <srchamberlain@impromed.com>
Cc: git@vger.kernel.org
Subject: Re: Can't get git to stop outputting to StdErr

"Scott R. Chamberlain" <srchamberlain@impromed.com> writes:

> The line I do is:
>
>     git push -q binaryRepo HEAD:"$Env:BUILD_SOURCEBRANCH"

This would 

 (1) squelch the output from the sending side (i.e. local), and

 (2) ask "quiet" to the receiving side (i.e. remote), if they know
     how to be quiet.

> But I get the following in my log after the build
>
>     2016-10-28T20:05:32.3179442Z ##[error]remote: 
>     remote: Analyzing objects... (3/3) (657 ms)        
>     remote: Storing packfile... done (40 ms)        
>     remote: Storing index... done (42 ms)        

These three lines prefixed with "remote:" are coming from the software that runs on the remote machine that accepts your push, but the way it says these three things do not look familiar to me.  Is it possible that the remote machine is running a Git server that is not ours, which lacks the support for "quiet" capability?  If that is the case, the symptom is understandable.

A quick archive search tells me that you are seeing the same issue as this one:

https://public-inbox.org/git/20160516133731.GA6903@sigill.intra.peff.net/

where the concluding remark, to which I agree, is:

    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.



-- 
Rely On Us.
ImproMed LLC
Henry Schein Animal Health
--


      parent reply	other threads:[~2016-12-19 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 20:31 Can't get git to stop outputting to StdErr Scott R. Chamberlain
2016-10-28 21:06 ` Junio C Hamano
2016-10-28 21:08   ` Scott R. Chamberlain
2016-12-19 14:56   ` Scott R. Chamberlain [this message]

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=77ad6aeef9a245f3adeab3751e7e94eb@ES5.impromed.com \
    --to=srchamberlain@impromed.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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