From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pdm-devel@lists.proxmox.com, Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [PATCH datacenter-manager] ui: pve: snapshots: description edit: close window on successful edit
Date: Tue, 26 May 2026 10:41:50 +0200 [thread overview]
Message-ID: <177978490367.129200.8610583402188215110.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260526082434.858047-1-d.csapak@proxmox.com>
On Tue, 26 May 2026 10:24:28 +0200, Dominik Csapak wrote:
> after updating the description of a snapshot, we have to change the
> view back to 'None', otherwise the edit dialog stays open.
>
>
Applied, thanks!
[1/1] ui: pve: snapshots: description edit: close window on successful edit
commit: 1660cbc890781b5696fc4fa088c832834ed0d8fc
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
prev parent reply other threads:[~2026-05-26 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 8:24 [PATCH datacenter-manager] ui: pve: snapshots: description edit: close window on successful edit Dominik Csapak
2026-05-26 8:41 ` Fabian Grünbichler [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=177978490367.129200.8610583402188215110.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pdm-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