From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH-SERIES qemu-server/manager/container] resize endpoint improvements
Date: Wed, 7 Jun 2023 19:29:37 +0200 [thread overview]
Message-ID: <b0b2818d-31a2-7246-30d0-e9c0bd8fbfdf@proxmox.com> (raw)
In-Reply-To: <20230530135207.87705-1-f.ebner@proxmox.com>
Am 30/05/2023 um 15:52 schrieb Fiona Ebner:
> Note that qemu-server path 2/2 is a breaking API change.
>
> qemu-server:
>
> Fiona Ebner (2):
> fix #517: api: allow resizing qcow2 disk with snapshots
> fix #2315: api: have resize endpoint spawn a worker task
>
> PVE/API2/Qemu.pm | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
>
> manager:
>
> Fiona Ebner (1):
> ui: override description for resize task
>
> www/manager6/Utils.js | 1 +
> 1 file changed, 1 insertion(+)
>
>
> container:
>
> Fiona Ebner (2):
> api: resize: drop error that can never apply
> api: resize: fork before locking
>
> src/PVE/API2/LXC.pm | 127 +++++++++++++++++++++++---------------------
> 1 file changed, 66 insertions(+), 61 deletions(-)
>
applied series, thanks!
prev parent reply other threads:[~2023-06-07 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 13:52 [pve-devel] " Fiona Ebner
2023-05-30 13:52 ` [pve-devel] [PATCH qemu-server 1/2] fix #517: api: allow resizing qcow2 disk with snapshots Fiona Ebner
2023-05-30 13:52 ` [pve-devel] [PATCH qemu-server 2/2] fix #2315: api: have resize endpoint spawn a worker task Fiona Ebner
2023-05-30 13:52 ` [pve-devel] [PATCH manager 1/1] ui: override description for resize task Fiona Ebner
2023-05-30 13:52 ` [pve-devel] [PATCH container 1/2] api: resize: drop error that can never apply Fiona Ebner
2023-05-30 13:52 ` [pve-devel] [PATCH container 2/2] api: resize: fork before locking Fiona Ebner
2023-06-07 17:29 ` Thomas Lamprecht [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=b0b2818d-31a2-7246-30d0-e9c0bd8fbfdf@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.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