From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-next? 0/2] qemu-img: Minor fixes to an amend error path
Date: Wed, 21 Nov 2018 10:48:07 +0100 [thread overview]
Message-ID: <20181121094807.GB4030@linux.fritz.box> (raw)
In-Reply-To: <20181119101921.31949-1-mreitz@redhat.com>
Am 19.11.2018 um 11:19 hat Max Reitz geschrieben:
> One of the amend error paths has two issues that are fixed by this
> series. Since they are relatively minor and have been present in 3.0
> already, I think there is no need to get them into 3.1. OTOH they are
> bug fixes, so they could go into 3.1 if you, dear reader, insist.
Thanks, applied to the block branch (looks like the dear reader
insists).
Kevin
prev parent reply other threads:[~2018-11-21 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 10:19 [Qemu-devel] [PATCH for-next? 0/2] qemu-img: Minor fixes to an amend error path Max Reitz
2018-11-19 10:19 ` [Qemu-devel] [PATCH for-next? 1/2] qemu-img: Fix typo Max Reitz
2018-11-19 10:19 ` [Qemu-devel] [PATCH for-next? 2/2] qemu-img: Fix leak Max Reitz
2018-11-21 1:23 ` [Qemu-devel] [Qemu-block] [PATCH for-next? 0/2] qemu-img: Minor fixes to an amend error path John Snow
2018-11-21 9:48 ` 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=20181121094807.GB4030@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).