From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>
Cc: "Junio C Hamano" <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCHv2] connect: display connection progress
Date: Thu, 10 May 2007 19:40:18 +0200 [thread overview]
Message-ID: <81b0412b0705101040g3a8426advc682d6560155d50c@mail.gmail.com> (raw)
In-Reply-To: <20070510150225.GS13655@mellanox.co.il>
On 5/10/07, Michael S. Tsirkin <mst@dev.mellanox.co.il> wrote:
>
> Do you really have git servers accessed over a local lan or on local system?
Yes and yes.
> I just use ssh in this case, and I think that's the common case ...
not on windows
> We *could* try doing something smart with non-blocking connect + select,
> and only print the message if it takes > 1 second. Are you
> sure it's worth the complication?
I'm not sure this suggestion of yours is worth the complication.
Besides, it's hard to get portably
next prev parent reply other threads:[~2007-05-10 17:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 19:52 [PATCH] connect: display connection progress Michael S. Tsirkin
2007-05-06 20:41 ` Junio C Hamano
2007-05-07 4:20 ` Michael S. Tsirkin
2007-05-10 9:51 ` [PATCHv2] " Michael S. Tsirkin
2007-05-10 11:39 ` Alex Riesen
2007-05-10 12:08 ` Michael S. Tsirkin
2007-05-10 12:19 ` Alex Riesen
2007-05-10 12:25 ` Michael S. Tsirkin
2007-05-10 13:33 ` Alex Riesen
2007-05-10 13:46 ` Michael S. Tsirkin
2007-05-10 14:16 ` Alex Riesen
2007-05-10 14:39 ` Michael S. Tsirkin
2007-05-10 14:52 ` Alex Riesen
2007-05-10 15:02 ` Michael S. Tsirkin
2007-05-10 17:40 ` Alex Riesen [this message]
2007-05-10 19:29 ` Junio C Hamano
2007-05-10 16:05 ` Linus Torvalds
2007-05-10 17:38 ` Alex Riesen
2007-05-06 22:21 ` [PATCH] " Alex Riesen
2007-05-07 4:54 ` Michael S. Tsirkin
2007-05-07 7:51 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81b0412b0705101040g3a8426advc682d6560155d50c@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mst@dev.mellanox.co.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).