From: Lou Lecrivain via pve-devel <pve-devel@lists.proxmox.com>
To: <s.hanreich@proxmox.com>, <pve-devel@lists.proxmox.com>
Cc: Lou.Lecrivain@wdz.de, jacobgreen@corporatetools.com
Subject: Re: [pve-devel] SPAM: [PATCH pve-network] ipam: fix #5496
Date: Thu, 5 Dec 2024 15:51:51 +0000 [thread overview]
Message-ID: <mailman.50.1733414141.332.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <0647bda8-60fd-4790-ba60-8c1c1efdd510@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 12374 bytes --]
From: <Lou.Lecrivain@wdz.de>
To: <s.hanreich@proxmox.com>, <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 15:51:51 +0000
Message-ID: <BE1P281MB211640AA780027373906B74885302@BE1P281MB2116.DEUP281.PROD.OUTLOOK.COM>
Hey Stefan,
Thanks for your input. I'll add this in the commit and submit a v2.
BR
________________________________________
De : Stefan Hanreich <s.hanreich@proxmox.com>
Envoyé : jeudi 5 décembre 2024 16:47
À : Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc : Lecrivain, Lou (WDZ) <Lou.Lecrivain@wdz.de>; jacobgreen@corporatetools.com <jacobgreen@corporatetools.com>
Objet : [!!ACHTUNG extern!!] - Re: [pve-devel] SPAM: [PATCH pve-network] ipam: fix #5496
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>
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-12-05 15:55 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
2024-12-05 15:51 ` Lou Lecrivain via pve-devel [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=mailman.50.1733414141.332.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=Lou.Lecrivain@wdz.de \
--cc=jacobgreen@corporatetools.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 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