From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexander Zeidler <a.zeidler@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs] faq: change to inline anchors to land on the actual questions
Date: Mon, 23 Oct 2023 17:39:59 +0200 [thread overview]
Message-ID: <fecccb62-732f-4903-8f1c-49d79df31622@proxmox.com> (raw)
In-Reply-To: <20231023153145.176237-1-a.zeidler@proxmox.com>
Am 23/10/2023 um 17:31 schrieb Alexander Zeidler:
> Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
> ---
> pve-faq.adoc | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/pve-faq.adoc b/pve-faq.adoc
> index 93fef32..2388673 100644
> --- a/pve-faq.adoc
> +++ b/pve-faq.adoc
> @@ -77,8 +77,7 @@ CPU.
> It is not limited to Linux guests but allows arbitrary operating systems
> to run.
>
> -[[faq-support-table]]
> -How long will my {pve} version be supported?::
> +[[faq-support-table]] How long will my {pve} version be supported?::
>
This breaks the package build here though:
unable to resolve chapter link (xref:faq-support-table)
our tooling probably needs to adapt detecting these inline refs too
prev parent reply other threads:[~2023-10-23 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 15:31 Alexander Zeidler
2023-10-23 15:39 ` 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=fecccb62-732f-4903-8f1c-49d79df31622@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.zeidler@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