From: Peter Maydell <peter.maydell@linaro.org>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/7] Block patches for 4.1.0-rc4
Date: Tue, 6 Aug 2019 12:53:42 +0100 [thread overview]
Message-ID: <CAFEAcA_BiNUZ_R4tX39hKMExBqMBpB-vLGeeDZ+0xwNRsehLEQ@mail.gmail.com> (raw)
In-Reply-To: <b4a2d9c1-a4ad-939b-64f4-c639e5bc4063@redhat.com>
On Tue, 6 Aug 2019 at 12:12, Max Reitz <mreitz@redhat.com> wrote:
>
> On 06.08.19 12:12, Peter Maydell wrote:
> > On Mon, 5 Aug 2019 at 18:01, Max Reitz <mreitz@redhat.com> wrote:
> >>
> >> On 05.08.19 18:59, Vladimir Sementsov-Ogievskiy wrote:
> >>> 05.08.2019 19:37, Max Reitz wrote:
> >>>> The following changes since commit 9bb68d34dda9be60335e73e65c8fb61bca035362:
> >>>>
> >>>> Merge remote-tracking branch 'remotes/philmd-gitlab/tags/edk2-next-20190803' into staging (2019-08-05 11:05:36 +0100)
> >>>>
> >>>> are available in the Git repository at:
> >>>>
> >>>> https://github.com/XanClic/qemu.git tags/pull-block-2019-08-05
> >>>>
> >>>> for you to fetch changes up to 07b0851c592efe188a87259adbda26a63c61dc92:
> >>>>
> >>>> block/backup: disable copy_range for compressed backup (2019-08-05 18:05:05 +0200)
> >>>>
> >>>> ----------------------------------------------------------------
> >>>> Block patches for 4.1.0-rc4:
> >>>> - Fix the backup block job when using copy offloading
> >>>> - Fix the mirror block job when using the write-blocking copy mode
> >>>> - Fix incremental backups after the image has been grown with the
> >>>> respective bitmap attached to it
> >>>>
> >>>> ----------------------------------------------------------------
> >>>> Max Reitz (5):
> >>>> backup: Copy only dirty areas
> >>>> iotests: Test backup job with two guest writes
> >>>> iotests: Test incremental backup after truncation
> >>>> mirror: Only mirror granularity-aligned chunks
> >>>> iotests: Test unaligned blocking mirror write
> >>>>
> >>>> Vladimir Sementsov-Ogievskiy (2):
> >>>> util/hbitmap: update orig_size on truncate
> >>>> block/backup: disable copy_range for compressed backup
> >>>>
> >>>
> >>> As I understand, this all should go to stable too? CC it.
> >> Ah, yes. Thanks.
> >
> > Are you planning to send a respin with the CC:stable tags?
> > (I did a test merge of this version which all passed OK.)
>
> I thought Vladimir just meant to physically CC qemu-stable on the series
> (which he did). Should I respin with the tags?
If you could do a quick respin that's probably most reliable --
I'm not sure exactly how the qemu-stable process works, though.
thanks
-- PMM
next prev parent reply other threads:[~2019-08-06 11:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 16:37 [Qemu-devel] [PULL 0/7] Block patches for 4.1.0-rc4 Max Reitz
2019-08-05 16:37 ` [Qemu-devel] [PULL 1/7] backup: Copy only dirty areas Max Reitz
2019-08-05 16:37 ` [Qemu-devel] [PULL 2/7] iotests: Test backup job with two guest writes Max Reitz
2019-08-05 16:37 ` [Qemu-devel] [PULL 3/7] util/hbitmap: update orig_size on truncate Max Reitz
2019-08-05 16:37 ` [Qemu-devel] [PULL 4/7] iotests: Test incremental backup after truncation Max Reitz
2019-08-05 16:37 ` [Qemu-devel] [PULL 5/7] mirror: Only mirror granularity-aligned chunks Max Reitz
2019-08-05 16:37 ` [Qemu-devel] [PULL 6/7] iotests: Test unaligned blocking mirror write Max Reitz
2019-08-05 16:37 ` [Qemu-devel] [PULL 7/7] block/backup: disable copy_range for compressed backup Max Reitz
2019-08-05 16:59 ` [Qemu-devel] [PULL 0/7] Block patches for 4.1.0-rc4 Vladimir Sementsov-Ogievskiy
2019-08-05 17:00 ` Max Reitz
2019-08-06 10:12 ` Peter Maydell
2019-08-06 11:12 ` Max Reitz
2019-08-06 11:53 ` Peter Maydell [this message]
2019-08-05 18:05 ` Peter Maydell
2019-08-05 18:06 ` Peter Maydell
2019-08-05 18:21 ` Max Reitz
2019-08-05 18:31 ` Peter Maydell
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=CAFEAcA_BiNUZ_R4tX39hKMExBqMBpB-vLGeeDZ+0xwNRsehLEQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=vsementsov@virtuozzo.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).