From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: jacobgreen@corporatetools.com
Subject: Re: [pve-devel] SPAM: [PATCH pve-network] ipam: fix #5496
Date: Thu, 5 Dec 2024 16:47:51 +0100 [thread overview]
Message-ID: <0647bda8-60fd-4790-ba60-8c1c1efdd510@proxmox.com> (raw)
In-Reply-To: <mailman.847.1732815873.391.pve-devel@lists.proxmox.com>
Thanks for sending the patch, ran this against my local instance and it
worked!
Consider this *commit*
Tested-by: Stefan Hanreich <s.hanreich@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-12-05 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 17:43 Lou Lecrivain via pve-devel
2024-12-05 15:47 ` Stefan Hanreich [this message]
2024-12-05 15:51 ` Lou Lecrivain via pve-devel
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=0647bda8-60fd-4790-ba60-8c1c1efdd510@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=jacobgreen@corporatetools.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