From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager 0/6] fixes/preparation extjs 7.0
Date: Thu, 27 May 2021 12:44:09 +0200 [thread overview]
Message-ID: <bf6d97c9-24e3-d236-1fc3-115b5d176df7@proxmox.com> (raw)
In-Reply-To: <20210526090112.23625-1-d.csapak@proxmox.com>
On 26.05.21 11:01, Dominik Csapak wrote:
> this series contains pve fixes/changes fror extjs7.0
>
> all of these patches should be backwards compatible with 6.0.1
>
> i tried to test every panel/button with extjs 7.0,
> but i am sure i forgot one or the other ;)
>
> Dominik Csapak (6):
> ui: form/VMCPUFlagSelector: mark radio-buttons as 'not form fields'
> ui: ResourceGrid: move first update to afterrender
> ui: panel/ConfigPanel: change ui class to pve-nav
> ui: panel/ConfigPanel: return early on no selection
> ui: tree/SnapshotTree: use beforedestroy instead of destroy
> ui: form/CalendarEvent: remove displayField from config
applied to master and stable-6, thanks!
prev parent reply other threads:[~2021-05-27 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 9:01 [pve-devel] " Dominik Csapak
2021-05-26 9:01 ` [pve-devel] [PATCH manager 1/6] ui: form/VMCPUFlagSelector: mark radio-buttons as 'not form fields' Dominik Csapak
2021-05-26 9:01 ` [pve-devel] [PATCH manager 2/6] ui: ResourceGrid: move first update to afterrender Dominik Csapak
2021-05-26 9:01 ` [pve-devel] [PATCH manager 3/6] ui: panel/ConfigPanel: change ui class to pve-nav Dominik Csapak
2021-05-26 9:01 ` [pve-devel] [PATCH manager 4/6] ui: panel/ConfigPanel: return early on no selection Dominik Csapak
2021-05-26 9:01 ` [pve-devel] [PATCH manager 5/6] ui: tree/SnapshotTree: use beforedestroy instead of destroy Dominik Csapak
2021-05-26 9:01 ` [pve-devel] [PATCH manager 6/6] ui: form/CalendarEvent: remove displayField from config Dominik Csapak
2021-05-27 10:44 ` 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=bf6d97c9-24e3-d236-1fc3-115b5d176df7@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal