Re: Git reports
- From
- Konstantin Khomoutov <flatworm@users.sourceforge.net>
- Date
- Dec 6, 2013, 17:00 UTC
- Message-ID
- <20131206210035.17413ee7bcdf3ca0c9655d81@domain007.com>
- In-Reply-To
- <CAMAQ3n+OtBdYALh4pg6kywtbgPtQjHr6Xc-2ff63df-h=TLwbA@mail.gmail.com>
On Fri, 6 Dec 2013 18:51:47 +0200 Muzaffer Tolga Ozses <tolga@ozses.net> wrote:
Show 9 quoted lines
> On another git server, I get reports like > Cloning into 'tcmb'... > remote: Counting objects: 704, done. > remote: Compressing objects: 100% (574/574), done. > remote: Total 704 (delta 369), reused 107 (delta 60) > Receiving objects: 100% (704/704), 129.99 KiB | 23 KiB/s, done. > 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). Or you pass the "-q" command-line option to `git clone`.