Re: [PATCHv2] connect: display connection progress

On 5/10/07, Michael S. Tsirkin [off-list ref] wrote:

quoted

quoted

Why not only on failure? IP addresses look ugly.

So you can see DNS problems you wanted to uncover.

I really just wanted git to tell me what it's doing,
so that I know it's not actually blocked on network,
not doing any work.

Aren't you interested in _what_ work is it doing?

quoted

DNS is all about mapping names to that ugly IP.

Yes, but so far git port does not seem to be commonly open
on random IPs ;).

Well, it does. It happened.

quoted

And DNS _problems_ often manifest themselves
by mapping the name to an unexpected IP.
Now that's really ugly

So, let's print the IP if -v is set?
Oh, look, now we'll have
NET_QUIET
NET_VERBOSE

No. All you have is QUIET and !QUIET (or VERBOSE and
!VERBOSE which is the same).

quoted

How about cleaning up this (reduce the amount of date
on screen)

Isn't this why we have -q?

Only fetch-pack has -q (and -v, which is confusing to
say the least).