On Fri, 6 Dec 2013 19:44:21 +0200
Muzaffer Tolga Ozses <to...@ozses.net> wrote:
> >> > Resolving deltas: 100% (369/369), done.
> >> >
> >> > whereas I don't get those with my own. What could I be doing
> >> > wrong?
> >> 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).
> > 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?
> stty tells me
> speed 38400 baud; line = 0;
> eol = M-^?; eol2 = M-^?; swtch = M-^?;
> ixany iutf8
> And I run identical commands on both servers, only URL changes.
OK, so we could supposedly rule out the possibility Git does not sense
it's connected to a terminal.
So let's do the next test: does
echo test >&2
print "test" on the box where Git does not report progress?
Another one: does Git report progress if you explicitly pass --progress
Does it work if you do
git clone $URL 2>&1
What Git and OS versions are on both machines?
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html