From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, kwolf@redhat.com
Subject: Re: [Qemu-devel] [PATCH] curl: fix curl read
Date: Thu, 9 May 2013 07:47:23 +0200 [thread overview]
Message-ID: <20130509054723.GA1074@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20130503112331.GA4517@fam-laptop.nay.redhat.com>
On Fri, May 03, 2013 at 07:23:31PM +0800, Fam Zheng wrote:
> On Fri, 05/03 13:09, Stefan Hajnoczi wrote:
> > On Fri, May 03, 2013 at 04:00:09PM +0800, Fam Zheng wrote:
> > > CURL library API has changed, the current curl driver is not working.
> > > This patch rewrites the use of API as well as the structure of internal
> > > states. (It is hard to split this to multiple patches as basically all
> > > these changes need to work together.)
> >
> > Which libcurl APIs have changed? I expect libcurl to be backwards
> > compatible.
>
> Function curl_multi_socket_all (see man 3 curl_multi_socket) is
> deprecated, and not working as I tried the current curl driver, build
> against libcurl 7.27.0. It's deprecated to be replaced by
> curl_multi_socket_action.
>
> The version does not concern, they are all introduced in the same
> version, 7.15.4 [1], and has been there for long.
>
> [1]: http://curl.haxx.se/libcurl/c/curl_multi_socket_action.html
Great, please include the details in the commit description.
I checked that RHEL 5.x has libcurl 7.15.5 so it should be safe to use
curl_multi_socket_action(). Most other operating systems will have a
newer libcurl than this.
Stefan
next prev parent reply other threads:[~2013-05-09 5:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 8:00 [Qemu-devel] [PATCH] curl: fix curl read Fam Zheng
2013-05-03 11:09 ` Stefan Hajnoczi
2013-05-03 11:23 ` Fam Zheng
2013-05-09 5:47 ` Stefan Hajnoczi [this message]
2013-05-09 6:41 ` Stefan Hajnoczi
2013-05-09 6:56 ` Fam Zheng
2013-05-09 15:16 ` Stefan Hajnoczi
2013-05-15 3:29 ` Fam Zheng
2013-05-15 7:46 ` 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=20130509054723.GA1074@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.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 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).