From: "Thomas Ellmenreich" <t.ellmenreich@proxmox.com>
To: <pve-devel@lists.proxmox.com>
Subject: superseded: [PATCH proxmox-acme v2] fix #7749: always serialize in same order
Date: Wed, 12 Aug 2026 13:56:04 +0200 [thread overview]
Message-ID: <DKMY2NUNA4Y1.2AMOPDFTLJHMT@proxmox.com> (raw)
In-Reply-To: <20260727072958.37999-1-t.ellmenreich@proxmox.com>
Superseded-by:
https://lore.proxmox.com/pve-devel/20260812115128.135004-1-t.ellmenreich@proxmox.com/T/#u
prev parent reply other threads:[~2026-08-12 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 7:29 [PATCH proxmox-acme v2] fix #7749: always serialize in same order Thomas Ellmenreich
2026-08-10 8:39 ` Elias Huhsovitz
2026-08-12 11:56 ` Thomas Ellmenreich [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=DKMY2NUNA4Y1.2AMOPDFTLJHMT@proxmox.com \
--to=t.ellmenreich@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