From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 8C95D1FF13F for ; Thu, 07 May 2026 12:34:10 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6D3FC137FE; Thu, 7 May 2026 12:34:08 +0200 (CEST) Message-ID: <17fd252b-a602-4c61-af75-15b6b4665142@proxmox.com> Date: Thu, 7 May 2026 12:34:02 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH pve-docs v4 01/17] qm: add anchor to "CPU Type" section To: Arthur Bied-Charreton , pve-devel@lists.proxmox.com References: <20260430160109.565536-1-a.bied-charreton@proxmox.com> <20260430160109.565536-2-a.bied-charreton@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: <20260430160109.565536-2-a.bied-charreton@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1778149935091 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.009 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: QQY6LRCI4FLYTSV7MWT42PVBOEVBEGC5 X-Message-ID-Hash: QQY6LRCI4FLYTSV7MWT42PVBOEVBEGC5 X-MailFrom: f.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Am 30.04.26 um 6:01 PM schrieb Arthur Bied-Charreton: > Allows frontend components to link directly to the "CPU Type" section, > instead of "CPU", which may be too broad for some usecases. > > Signed-off-by: Arthur Bied-Charreton > --- > qm.adoc | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/qm.adoc b/qm.adoc > index e6b7918..7d7f61b 100644 > --- a/qm.adoc > +++ b/qm.adoc > @@ -441,6 +441,7 @@ list can contain numbers but also number ranges. For example, the *affinity* > `0-1,8-11` (expanded `0, 1, 8, 9, 10, 11`) would allow the VM to run on only > these six specific host cores. > > +[[qm_cpu_type]] > CPU Type > ^^^^^^^^ > Since the implicit '_cpu_type' anchor already exists and was linkable, I think we need to stick to that to avoid breaking existing links on the internet. So this should become [[_cpu_type]].