From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs/proxmox-firewall v2 0/4] migrate proxmox-firewall to proxmox-log + introduce subcommands
Date: Tue, 29 Jul 2025 08:21:29 +0200 [thread overview]
Message-ID: <175377008747.1884646.12372072916902152630.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250527135800.190084-1-s.hanreich@proxmox.com>
On Tue, 27 May 2025 15:57:56 +0200, Stefan Hanreich wrote:
> Since we now have proxmox-log as the standard crate for logging purposes,
> migrate proxmox-firewall to the new logging crate.
>
> The old logging setup was also tied with the debugging mechanisms described in
> the documentation. I used that opportunity to implement specific subcommands for
> debugging proxmox-firewall, instead of just relying solely on the log output.
>
> [...]
A slightlier more convenient ping might have been sending a rebased v3, albeit
it naturally could have been also looked at earlier, but IMO this better fits a
new major release anyway.
Applied, with dependencies updated for trixie and d/control and Cargo.toml
conflicts resolved, thanks!
[1/1] firewall: update 'useful commands' section with new subcommands
commit: 0e3aaccaaed89e8df0028e03dccfcc8b5a12faa8
[1/3] firewall: use proxmox_log
commit: cf57c86cb4592c603ea78e4ece707d1659f58f99
[2/3] proxmox-firewall: add subcommands
commit: 7035e7de3e9f13ace14681141006eed2dc84e60a
[3/3] proxmox-firewall: add localnet subcommand
commit: f0ac2be37a2f0d188d087534a080050cd1327e21
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-29 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 13:57 Stefan Hanreich
2025-05-27 13:57 ` [pve-devel] [PATCH proxmox-firewall v2 1/3] firewall: use proxmox_log Stefan Hanreich
2025-05-27 13:57 ` [pve-devel] [PATCH proxmox-firewall v2 2/3] proxmox-firewall: add subcommands Stefan Hanreich
2025-05-27 13:57 ` [pve-devel] [PATCH proxmox-firewall v2 3/3] proxmox-firewall: add localnet subcommand Stefan Hanreich
2025-05-27 13:58 ` [pve-devel] [PATCH pve-docs v2 1/1] firewall: update 'useful commands' section with new subcommands Stefan Hanreich
2025-07-24 15:09 ` [pve-devel] [PATCH docs/proxmox-firewall v2 0/4] migrate proxmox-firewall to proxmox-log + introduce subcommands Stefan Hanreich
2025-07-29 6:21 ` 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=175377008747.1884646.12372072916902152630.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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