qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: armbru@redhat.com
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
	qemu-block@nongnu.org, agraf@suse.de
Subject: [Qemu-devel] [PATCH v3 0/2] block/curl: Don't lose original error when a connection fails.
Date: Wed,  8 Jul 2015 13:50:41 +0100	[thread overview]
Message-ID: <1436359843-15612-1-git-send-email-rjones@redhat.com> (raw)

Since v2:

This adds a generalized anti-flooding mechanism, and then uses it to
ensure that curl errors wouldn't flood the log files.

Rich.

             reply	other threads:[~2015-07-08 12:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 12:50 Richard W.M. Jones [this message]
2015-07-08 12:50 ` [Qemu-devel] [PATCH v3 1/2] Add a simple mechanism to protect against error message floods Richard W.M. Jones
2015-07-08 13:26   ` Kevin Wolf
2015-07-08 13:38     ` Paolo Bonzini
2015-07-08 12:50 ` [Qemu-devel] [PATCH v3 2/2] block/curl: Don't lose original error when a connection fails Richard W.M. Jones

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=1436359843-15612-1-git-send-email-rjones@redhat.com \
    --to=rjones@redhat.com \
    --cc=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).