From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu 1/2] generate and ship static list of CPU models
Date: Wed, 11 Feb 2026 11:33:31 +0100 [thread overview]
Message-ID: <b28b77e4-26ee-462d-8229-c6f8f4f78b0c@proxmox.com> (raw)
In-Reply-To: <20260210135417.184127-2-f.ebner@proxmox.com>
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.
next prev parent reply other threads:[~2026-02-11 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 13:52 [PATCH-SERIES qemu/qemu-server 0/2] generate and ship static list of CPU models with pve-qemu-kvm Fiona Ebner
2026-02-10 13:52 ` [PATCH qemu 1/2] generate and ship static list of CPU models Fiona Ebner
2026-02-11 10:33 ` Thomas Lamprecht [this message]
2026-02-11 11:41 ` Fiona Ebner
2026-02-17 18:28 ` applied: " Thomas Lamprecht
2026-02-10 13:52 ` [PATCH qemu-server 2/2] cpu config: use static CPU model list shipped by QEMU package if available Fiona Ebner
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=b28b77e4-26ee-462d-8229-c6f8f4f78b0c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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.