From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 0/2] Improve route map documentation
Date: Wed, 13 May 2026 18:20:09 +0200 [thread overview]
Message-ID: <20260513162013.456890-1-s.hanreich@proxmox.com> (raw)
Removed the misleading note about having to create an explicit deny entry when
calling a route map and also added a small section mentioning that every route
map has an empty deny entry as its last entry.
pve-docs:
Stefan Hanreich (2):
sdn: route maps: mention implicit deny default explicitly
sdn: route map: delete note about creating an empty deny entry
pvesdn.adoc | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
Summary over all repositories:
1 files changed, 2 insertions(+), 7 deletions(-)
--
Generated by murpp 0.11.0
next reply other threads:[~2026-05-13 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 16:20 Stefan Hanreich [this message]
2026-05-13 16:20 ` [PATCH pve-docs 1/2] sdn: route maps: mention implicit deny default explicitly Stefan Hanreich
2026-05-13 16:20 ` [PATCH pve-docs 2/2] sdn: route map: delete note about creating an empty deny entry Stefan Hanreich
2026-05-13 16:48 ` applied: [PATCH docs 0/2] Improve route map documentation 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=20260513162013.456890-1-s.hanreich@proxmox.com \
--to=s.hanreich@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.