From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-docs 1/1] network: update name of pinning tool
Date: Tue, 5 Aug 2025 15:35:24 +0200 [thread overview]
Message-ID: <175440092221.3069018.9900282304290537293.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250805122701.231702-1-s.hanreich@proxmox.com>
On Tue, 05 Aug 2025 14:26:58 +0200, Stefan Hanreich wrote:
> Has been changed from proxmox-network-interface-pinning to
> pve-network-interface-pinning for the initial release, since we do not
> include the standalone rust tool for now.
>
>
Applied, thanks!
[1/1] network: update name of pinning tool
commit: 3f1bf7305d4149682b37fba9c42f816f17920261
_______________________________________________
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-08-05 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 12:26 [pve-devel] " Stefan Hanreich
2025-08-05 13:35 ` 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=175440092221.3069018.9900282304290537293.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