From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Date: Fri, 06 Dec 2013 17:09:58 GMT
Subject: Re: Git reports
Message-ID: <20131206210958.59f553060e3802d56f4a53b8@domain007.com>
In-Reply-To: <20131206210035.17413ee7bcdf3ca0c9655d81@domain007.com>

On Fri, 6 Dec 2013 21:00:35 +0400
Konstantin Khomoutov <flatworm@users.sourceforge.net> wrote:

[...]
> > Resolving deltas: 100% (369/369), done.
> > 
> > whereas I don't get those with my own. What could I be doing wrong?
> 
> The documentation on `git push` states:
> 
>   --progress
> 
>     Progress status is reported on the standard error stream by
> default when it is attached to a terminal, unless -q is specified.
> This flag forces progress status even if the standard error stream is
> not directed to a terminal.
> 
> So it might turn out on your own server Git for some reason fails to
> figure out its standard error stream is connected to a terminal.
> Or, the error stream of your shell process is redirected somewhere
> (and hence inherited by Git).

To underline the fact this is not all too unlikely, you're able to
completely silence error reports in your shell prompt by executing

  exec 2>/dev/null

(you can regain it back by doing `exec 2>&1`).

So you might face a misbehaving shell logon script for instance.

As to whether Git senses the TTY -- what does running

  stty

tells you?  Does it fail with something like "inappropriate ioctl for
device" or prints a couple of settings?