09.06.2021 19:40, Vladimir Sementsov-Ogievskiy wrote:
09.06.2021 18:53, Kevin Wolf wrote:
Am 14.05.2021 um 17:53 hat Vladimir Sementsov-Ogievskiy geschrieben:
Hi Alberto!
What are your plans for v5? I'm now finishing a new series which makes
backup-top filter public, and I want to base it on your series
(otherwise I can't add a test).
Berto, where are we with this? I see that Vladimir picked up one or two
patches for his series, but I think we still need a v5 at least for the
rest?
If you can't find the time, should someone else pick up all patches?
Kevin
My "[PATCH v5 0/9] Allow changing bs->file on reopen" supersedes the "subject" part of
the series. I think we now should start from taking it. Hmm, and I should check, does it conflict with recently
merged block-permission-folloup and with beginning of "[PATCH v4 00/35] block: publish backup-top
filter" which is already almost reviewed by Max and should land soon I hope (ohh, seems I should issue v5
for python conflictes).
So, I propose the following plan:
1. I'll rebase and send "block: publish backup-top filter" series
today-tomorrow. It's big, and mostly reviewed, let's not lose r-bs by rebases.
2. I'll rebase and send if needed (if it conflicts with master and/or [1]) "[PATCH v5
0/9] Allow changing bs->file on reopen"
3. Then we'll decide what to do with the rest. Finally, I can take it if I have
some time (the head is spinning from the number of tasks ;)
I also think that we can drop x- prefix even without supporting of multiple
reopen, and implement it later as an option. QAPI interface is powerful enough
for such enhancements.
[1] and [2] done, patches sent. Finally, "[PATCH v6 0/9] Allow changing bs->file on
reopen" depends only on two first simple patches of "[PATCH v5 00/35] block: publish
backup-top filter", so the series may go in parallel.
--
Best regards,
Vladimir