From: "Richard W.M. Jones" <rjones@redhat.com>
To: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Qemu Devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] block.curl: adding 'timeout' option
Date: Tue, 26 Aug 2014 21:32:37 +0100 [thread overview]
Message-ID: <20140826203236.GL14001@redhat.com> (raw)
In-Reply-To: <1407944667-17932-2-git-send-email-danielhb@linux.vnet.ibm.com>
On Wed, Aug 13, 2014 at 12:44:27PM -0300, Daniel Henrique Barboza wrote:
> The curl hardcoded timeout (5 seconds) sometimes is not long
> enough depending on the remote server configuration and network
> traffic. The user should be able to set how much long he is
> willing to wait for the connection.
>
> Adding a new option to set this timeout gives the user this
> flexibility. The previous default timeout of 5 seconds will be
> used if this option is not present.
>
> Reviewed-by: Fam Zheng <famz@redhat.com>
> Signed-off-by: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
You can add:
Tested-by: Richard W.M. Jones <rjones@redhat.com>
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
next prev parent reply other threads:[~2014-08-26 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 15:44 [Qemu-devel] [PATCH v3] block.curl: timeout option Daniel Henrique Barboza
2014-08-13 15:44 ` [Qemu-devel] [PATCH v3] block.curl: adding 'timeout' option Daniel Henrique Barboza
2014-08-14 13:32 ` Benoît Canet
2014-08-26 20:32 ` Richard W.M. Jones [this message]
2014-08-27 9:40 ` [Qemu-devel] [PATCH v3] block.curl: timeout option Stefan Hajnoczi
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=20140826203236.GL14001@redhat.com \
--to=rjones@redhat.com \
--cc=danielhb@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.