From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
qemu-stable@nongnu.org, Eric Blake <eblake@redhat.com>,
Kevin Wolf <kwolf@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/2] qemu-img: Resolve relative backing paths in rebase
Date: Wed, 9 May 2018 20:20:00 +0200 [thread overview]
Message-ID: <20180509182002.8044-1-mreitz@redhat.com> (raw)
v1 of the cover letter here (no change necessary there):
http://lists.nongnu.org/archive/html/qemu-block/2018-05/msg00243.html
v2: Fixed a leaked buffer in an error path in patch 1 [Eric]
git-backport-diff against v1:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/2:[0001] [FC] 'qemu-img: Resolve relative backing paths in rebase'
002/2:[----] [--] 'iotests: Add test for rebasing with relative paths'
Max Reitz (2):
qemu-img: Resolve relative backing paths in rebase
iotests: Add test for rebasing with relative paths
qemu-img.c | 23 ++++++++++++-
tests/qemu-iotests/024 | 82 ++++++++++++++++++++++++++++++++++++++++++++--
tests/qemu-iotests/024.out | 30 +++++++++++++++++
3 files changed, 131 insertions(+), 4 deletions(-)
--
2.14.3
next reply other threads:[~2018-05-09 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 18:20 Max Reitz [this message]
2018-05-09 18:20 ` [Qemu-devel] [PATCH v2 1/2] qemu-img: Resolve relative backing paths in rebase Max Reitz
2018-05-09 18:51 ` Eric Blake
2018-05-09 19:20 ` Max Reitz
2018-05-09 18:20 ` [Qemu-devel] [PATCH v2 2/2] iotests: Add test for rebasing with relative paths Max Reitz
2018-06-01 11:13 ` [Qemu-devel] [PATCH v2 0/2] qemu-img: Resolve relative backing paths in rebase Max Reitz
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=20180509182002.8044-1-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@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 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.