public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] applied: SPAM: [PATCH pve-network v3 3/4] fix: register details in pve ipam db for add_next_freeip
Date: Mon,  7 Apr 2025 18:28:33 +0200	[thread overview]
Message-ID: <174404279725.2967426.4115819053996056694.b4-ty@proxmox.com> (raw)
In-Reply-To: <mailman.187.1734119229.332.pve-devel@lists.proxmox.com>

On Fri, 13 Dec 2024 20:45:39 +0100, lou lecrivain via pve-devel wrote:
> 


Applied, thanks!

[1/1] SPAM: [PATCH pve-network v3 3/4] fix: register details in pve ipam db for add_next_freeip
      commit: 5a050f4d4c6bc315df27d9950af1796486c95712


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-04-07 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241213194539.43105-2-lou.lecrivain@wdz.de>
2024-12-13 19:45 ` [pve-devel] SPAM: [PATCH pve-network v3 2/4] dhcp: always generate dhcp-range for dnsmasq lou lecrivain via pve-devel
2025-04-07 16:28   ` [pve-devel] applied: " Thomas Lamprecht
2024-12-13 19:45 ` [pve-devel] SPAM: [PATCH pve-network v3 3/4] fix: register details in pve ipam db for add_next_freeip lou lecrivain via pve-devel
2025-04-07 16:28   ` Thomas Lamprecht [this message]
2024-12-13 19:45 ` [pve-devel] SPAM: [PATCH pve-network v3 4/4] update tests following changes to behaviour: - allocating IPs also when prefix-only - PVE IPAM register details for every allocation strategy lou lecrivain via pve-devel
2025-04-07 16:28   ` [pve-devel] applied: " Thomas Lamprecht

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=174404279725.2967426.4115819053996056694.b4-ty@proxmox.com \
    --to=t.lamprecht@proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal