From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 4C3B91FF13B for ; Wed, 11 Feb 2026 11:32:56 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7334F18624; Wed, 11 Feb 2026 11:33:38 +0100 (CET) Message-ID: Date: Wed, 11 Feb 2026 11:33:31 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: [PATCH qemu 1/2] generate and ship static list of CPU models To: Fiona Ebner , pve-devel@lists.proxmox.com References: <20260210135417.184127-1-f.ebner@proxmox.com> <20260210135417.184127-2-f.ebner@proxmox.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <20260210135417.184127-2-f.ebner@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: 1770805925675 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.020 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: QUSBCY3ORIUHDJOQJYRKS5PUEB5H6SAW X-Message-ID-Hash: QUSBCY3ORIUHDJOQJYRKS5PUEB5H6SAW X-MailFrom: t.lamprecht@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 10.02.26 um 14:53 schrieb Fiona Ebner: > Fail the build when the list changes, so that new models can be > picked up selectively and other changes that might require adaptations > are not missed. thanks, any objection in storing this as pretty-formatted json? As then the default line-based git diff is making comparisons simpler, as while word-diff is great, it has it's limits IMO. No need for a v2 in any case, as that change is easy enough to squash in. btw. starting to wonder if we should produce an extra architecture "all" packages for such files, could reduce churn on selective uploads; but I'd figure that the current rate of change will slow down a bit soon.