All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, stefanha@redhat.com,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: Fix blockdev-backup not to use funky error class
Date: Tue, 17 Mar 2015 08:49:56 +0100	[thread overview]
Message-ID: <87oansjc63.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1426577774-21605-1-git-send-email-armbru@redhat.com> (Markus Armbruster's message of "Tue, 17 Mar 2015 08:36:14 +0100")

I should mention that I hunted down all new instances of funky error
classes since 2.2.  This is the last one.  The other two are:

[PATCH] vnc: Fix QMP change not to use funky error class
[PATCH] block: Fix block-set-write-threshold not to use funky error class

  reply	other threads:[~2015-03-17  7:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17  7:36 [Qemu-devel] [PATCH] block: Fix blockdev-backup not to use funky error class Markus Armbruster
2015-03-17  7:49 ` Markus Armbruster [this message]
2015-03-19 11:29 ` Kevin Wolf
2015-03-19 11:51   ` Markus Armbruster
2015-03-19 14:22   ` Eric Blake

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=87oansjc63.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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.