Re: [PATCHv2] connect: display connection progress

From: Alex Riesen <raa.lkml@gmail.com>
Date: May 10, 2007, 14:16 UTC
Message-ID: <81b0412b0705100716t680290a3qd1d10cf588a65f5a@mail.gmail.com>
In-Reply-To: <20070510134622.GN13655@mellanox.co.il>

On 5/10/07, Michael S. Tsirkin <mst@dev.mellanox.co.il> wrote:

Show 7 quoted lines

> > >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?

> > 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.

Show 8 quoted lines

> > 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).

> > 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).