all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs/manager 0/7] interface-pinning: add rename subcommand and man(1) page
Date: Tue, 23 Jun 2026 11:43:17 +0200	[thread overview]
Message-ID: <20260623094419.330174-1-c.heiss@proxmox.com> (raw)

It came up a few times in the forum already to be able to rename
already-pinned interfaces, which is sensible.

While at it, also add a full man(1) page for
pve-network-interface-pinning. Currently, it's just a hardcoded stub
without any actual help text.

pve-docs:

Christoph Heiss (4):
  network: fix typo occurences -> occurrences
  pve-doc-generator: handle CLI tools/services with dashes in their name
  pve-network-interface-pinning: init man(1) page
  network: pinning: mention how to rename an interface

 ...-network-interface-pinning.1-synopsis.adoc | 50 ++++++++++++++++
 pve-admin-guide.adoc                          |  8 +++
 pve-doc-generator.mk.in                       | 12 ++--
 pve-network-interface-pinning.adoc            | 60 +++++++++++++++++++
 pve-network.adoc                              |  8 ++-
 5 files changed, 131 insertions(+), 7 deletions(-)
 create mode 100644 generated/pve-network-interface-pinning.1-synopsis.adoc
 create mode 100644 pve-network-interface-pinning.adoc

pve-manager:

Christoph Heiss (3):
  network-interface-pinning: avoid warning if `bond-primary` is unset
  network-interface-pinning: add method for renaming existing pins
  network-interface-pinning: generate proper manpage from docs

 PVE/CLI/pve_network_interface_pinning.pm | 156 +++++++++++++++++------
 bin/Makefile                             |  19 ---
 2 files changed, 119 insertions(+), 56 deletions(-)
-- 




             reply	other threads:[~2026-06-23  9:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23  9:43 Christoph Heiss [this message]
2026-06-23  9:43 ` [PATCH docs 1/7] network: fix typo occurences -> occurrences Christoph Heiss
2026-06-23  9:43 ` [PATCH docs 2/7] pve-doc-generator: handle CLI tools/services with dashes in their name Christoph Heiss
2026-06-23  9:43 ` [PATCH docs 3/7] pve-network-interface-pinning: init man(1) page Christoph Heiss
2026-06-23  9:43 ` [PATCH docs 4/7] network: pinning: mention how to rename an interface Christoph Heiss
2026-06-23  9:43 ` [PATCH manager 5/7] network-interface-pinning: avoid warning if `bond-primary` is unset Christoph Heiss
2026-06-23  9:43 ` [PATCH manager 6/7] network-interface-pinning: add method for renaming existing pins Christoph Heiss
2026-06-23  9:43 ` [PATCH manager 7/7] network-interface-pinning: generate proper manpage from docs Christoph Heiss

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=20260623094419.330174-1-c.heiss@proxmox.com \
    --to=c.heiss@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 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