From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Daniel Krambrock <krambrod@staff.uni-marburg.de>
Subject: Re: [pve-devel] [PATCH firewall 1/1] fix #5335: sort cluster.fw entries in ALIASES section
Date: Mon, 15 Apr 2024 13:36:07 +0200 (CEST) [thread overview]
Message-ID: <1201594547.6978.1713180967636@webmail.proxmox.com> (raw)
In-Reply-To: <mailman.326.1712824628.450.pve-devel@lists.proxmox.com>
> Daniel Krambrock via pve-devel <pve-devel@lists.proxmox.com> hat am 11.04.2024 10:09 CEST geschrieben:
Hi!
for both this and the access-control patch, please add
- *some* commit message (e.g., something like "stable sorting in XX config file allows tracking changes by checking into git or when using automation like ansible" would be enough. try to describe the *why*, rather than the *what* - the latter is usually obvious when looking at the diff, especially for such small patches ;))
- add your Signed-off-by trailer ("git commit --amend -s" should do the trick)
note that you don't need to send a cover letter for single patches, those are just needed when you send bigger patch series where it makes sense to summarize all the patches to get a quick overview of the overall aim of the series.
thanks!
> ---
> src/PVE/Firewall.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/PVE/Firewall.pm b/src/PVE/Firewall.pm
> index 77cbaf4..81a8798 100644
> --- a/src/PVE/Firewall.pm
> +++ b/src/PVE/Firewall.pm
> @@ -3360,7 +3360,7 @@ my $format_aliases = sub {
> my $raw = '';
>
> $raw .= "[ALIASES]\n\n";
> - foreach my $k (keys %$aliases) {
> + foreach my $k (sort keys %$aliases) {
> my $e = $aliases->{$k};
> $raw .= "$e->{name} $e->{cidr}";
> $raw .= " # " . encode('utf8', $e->{comment})
> --
> 2.39.2
parent reply other threads:[~2024-04-15 11:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.326.1712824628.450.pve-devel@lists.proxmox.com>]
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=1201594547.6978.1713180967636@webmail.proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=krambrod@staff.uni-marburg.de \
--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