From: Deepen Dhulla <deepen@deependhulla.com>
Cc: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] Unsubscribe
Date: Thu, 16 Nov 2023 13:58:09 +0530 [thread overview]
Message-ID: <CA+gGJo-9vTVAMzZ7RgRkpK5YrYvxL79RUvqzc8xs6VJZTbn4wQ@mail.gmail.com> (raw)
In-Reply-To: <d4e92eae-80db-46de-b6c1-7646f4f9e9fa@proxmox.com>
[-- Attachment #1: Type: text/plain, Size: 2393 bytes --]
On Tue, 14 Nov 2023 at 9:15 PM, Thomas Lamprecht <t.lamprecht@proxmox.com>
wrote:
> Am 09/08/2023 um 12:55 schrieb Christian Ebner:
> > This series is send to pmg-devel and pve-devel list, as it changes the
> > DateTimeField used by Proxmox Virtual Environment and Proxmox Mail
> > Gateway.
> >
> > This series of patches implements functionality to extend the firewall
> > log panel to filter the logs by date and time.
> >
> > The series consists of patches for the proxmox-widget-toolkit and
> > patches for pve-manager and pmg-gui which depend on the changes to
> > proxmox-widget-toolkit.
> >
> > proxmox-widget-toolkit:
> > The DateTimeField component is reworked to be more declarative and
> > formula and data bindings are utilized to update state changes between
> > parent and child components.
> > The LogView component is extended to control if the date/time based
> > filtering should be shown (as for example the Ceph logs use the same
> > panel, but filters should not be shown), and to configure the submit
> > values for api calls.
> >
> > pve-manager:
> > The neccessary configs are set to show the filters in the panel and the
> > correct submit format for api call.
> >
> > pmg-gui:
> > Revert a commit, introduced to fix a side effect of one of the patches
> > from the previous version of the patches, which got applied.
> >
> > proxmox-widget-toolkit:
> > Christian Ebner (2):
> > fix #4442: adapt DateTimeField to be more declarative
> > fix #4442: Extend LogView for firewall datetime filtering
> >
> > src/form/DateTimeField.js | 281 ++++++++++++++++----------------------
> > src/panel/LogView.js | 89 ++++++++++--
> > 2 files changed, 201 insertions(+), 169 deletions(-)
> >
> > pve-manager:
> > Christian Ebner (1):
> > fix #4442: Add date-time filtering for firewall logs
> >
> > www/manager6/node/Config.js | 2 ++
> > www/manager6/qemu/Config.js | 2 ++
> > 2 files changed, 4 insertions(+)
> >
> > pmg-gui:
> > Christian Ebner (1):
> > Revert "fix tracking center with newer proxmox-widget-toolkit"
> >
> > js/MailTracker.js | 2 --
> > 1 file changed, 2 deletions(-)
> >
>
>
> applied, thanks!
>
>
> _______________________________________________
> pmg-devel mailing list
> pmg-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
>
>
[-- Attachment #2: Type: text/html, Size: 3160 bytes --]
next prev parent reply other threads:[~2023-11-16 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 10:55 [pmg-devel] [PATCH v2 proxmox-widget-toolkit manager pmg-gui 0/4] #4442: impl firewall log filtering Christian Ebner
2023-08-09 10:55 ` [pmg-devel] [PATCH v2 proxmox-widget-toolkit 1/2] fix #4442: adapt DateTimeField to be more declarative Christian Ebner
2023-08-09 10:55 ` [pmg-devel] [PATCH v2 proxmox-widget-toolkit 2/2] fix #4442: Extend LogView for firewall datetime filtering Christian Ebner
2023-08-09 10:55 ` [pmg-devel] [PATCH v2 manager 3/3] fix #4442: Add date-time filtering for firewall logs Christian Ebner
2023-08-09 10:55 ` [pmg-devel] [PATCH v2 pmg-gui 4/4] Revert "fix tracking center with newer proxmox-widget-toolkit" Christian Ebner
2023-11-09 9:22 ` [pmg-devel] [PATCH v2 proxmox-widget-toolkit manager pmg-gui 0/4] #4442: impl firewall log filtering Christian Ebner
2023-11-14 15:45 ` [pmg-devel] applied: [pve-devel] " Thomas Lamprecht
2023-11-16 8:28 ` Deepen Dhulla [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-18 8:13 [pmg-devel] unsubscribe Heiko Siewert
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=CA+gGJo-9vTVAMzZ7RgRkpK5YrYvxL79RUvqzc8xs6VJZTbn4wQ@mail.gmail.com \
--to=deepen@deependhulla.com \
--cc=pmg-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