From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH widget-toolkit 1/1] inputpanel: improve validitychange check for advanced fields
Date: Fri, 10 Mar 2023 15:45:15 +0100 [thread overview]
Message-ID: <0f31c2db-cf3b-5ee4-17f7-6e89f9ebf4a5@proxmox.com> (raw)
In-Reply-To: <20230310140808.2245916-1-d.csapak@proxmox.com>
nice. now the advanced part doesn't open on create or edit anymore :)
for both patches:
Tested-By: Aaron Lauterer <a.lauterer@proxmox.com>
next prev parent reply other threads:[~2023-03-10 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 14:08 Dominik Csapak
2023-03-10 14:08 ` [pve-devel] [PATCH manager 1/1] ui: ceph: pool: don't always show advanced fields on create Dominik Csapak
2023-03-11 16:39 ` [pve-devel] applied: " Thomas Lamprecht
2023-03-10 14:45 ` Aaron Lauterer [this message]
2023-03-11 16:33 ` [pve-devel] applied: [PATCH widget-toolkit 1/1] inputpanel: improve validitychange check for advanced fields Thomas Lamprecht
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=0f31c2db-cf3b-5ee4-17f7-6e89f9ebf4a5@proxmox.com \
--to=a.lauterer@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