From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Lukas Wagner <l.wagner@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager 2/4] ui: sdn: fix onlineHelp anchors
Date: Tue, 21 Nov 2023 17:37:51 +0100 [thread overview]
Message-ID: <95a759c5-e2a5-4c37-affa-d620949a1a1a@proxmox.com> (raw)
In-Reply-To: <20231121144758.243333-3-l.wagner@proxmox.com>
Am 21/11/2023 um 15:47 schrieb Lukas Wagner:
> These have been renamed in:
> bcb72b 'sdn: overall language and consistency rework' in pve-docs
I reverted that part in the docs before I saw you patch and will keep it that
way, IMO one should have good reasons to break links than just vnet vs vnets..
next prev parent reply other threads:[~2023-11-21 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 14:47 [pve-devel] [PATCH docs/manager/proxmox-widget-toolkit 0/4] notifications: add help buttons, linking to the appropriate sections Lukas Wagner
2023-11-21 14:47 ` [pve-devel] [PATCH pve-docs 1/4] notification: add anchors for target types/matchers Lukas Wagner
2023-11-21 16:37 ` [pve-devel] applied: " Thomas Lamprecht
2023-11-21 14:47 ` [pve-devel] [PATCH pve-manager 2/4] ui: sdn: fix onlineHelp anchors Lukas Wagner
2023-11-21 16:37 ` Thomas Lamprecht [this message]
2023-11-21 14:47 ` [pve-devel] [PATCH pve-manager 3/4] ui: dc: config: remove onlineHelp for notification config view Lukas Wagner
2023-11-21 16:38 ` [pve-devel] applied: " Thomas Lamprecht
2023-11-21 14:47 ` [pve-devel] [PATCH proxmox-widget-toolkit 4/4] notification ui: add appropriate onlineHelp anchors Lukas Wagner
2023-11-21 19:52 ` [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=95a759c5-e2a5-4c37-affa-d620949a1a1a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@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.