From: Kevin Wolf <kwolf@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] curl: Don't set curl options on the handle just before it's going to be deleted.
Date: Tue, 11 Jun 2013 10:22:47 +0200 [thread overview]
Message-ID: <20130611082247.GC2379@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1370882415-15463-1-git-send-email-rjones@redhat.com>
Am 10.06.2013 um 18:40 hat Richard W.M. Jones geschrieben:
> From: "Richard W.M. Jones" <rjones@redhat.com>
>
> (Found by Kamil Dudka)
>
> Signed-off-by: Richard W.M. Jones <rjones@redhat.com>
> Cc: Michael Tokarev <mjt@tls.msk.ru>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2013-06-11 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 16:40 [Qemu-devel] [PATCH v2] curl: Don't set curl options on the handle just before it's going to be deleted Richard W.M. Jones
2013-06-11 7:50 ` Stefan Hajnoczi
2013-06-11 8:22 ` Kevin Wolf [this message]
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=20130611082247.GC2379@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--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).