From: windy via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: windy <me@doublemine.me>
Subject: [pve-devel] Offer to test patch series for Bug 5076 (v2/v3)
Date: Tue, 19 Aug 2025 01:45:28 +0000 [thread overview]
Message-ID: <mailman.219.1755767263.385.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 5735 bytes --]
From: windy <me@doublemine.me>
To: pve-devel@lists.proxmox.com
Subject: Offer to test patch series for Bug 5076 (v2/v3)
Date: Tue, 19 Aug 2025 01:45:28 +0000
Message-ID: <01060198c000b456-912e4f31-cee4-4875-b6f2-69e1c36a3ede-000000@ap-northeast-1.amazonses.com>
Dear Proxmox Development Team,
I am writing in response to the developer's post regarding the patch series
for Bug 5076 .
I would like to volunteer to test the v2 patch series, or the upcoming v3,
to help validate the fix. I'm happy to provide feedback on its
effectiveness.
Link to v2:
https://lore.proxmox.com/all/999303783.1030.1748874882155@webmail.proxmox.com/
<https://www.google.com/url?sa=E&q=https%3A%2F%2Flore.proxmox.com%2Fall%2F999303783.1030.1748874882155%40webmail.proxmox.com%2F>
Link to Bugzilla: https://bugzilla.proxmox.com/show_bug.cgi?id=5076
<https://www.google.com/url?sa=E&q=https%3A%2F%2Fbugzilla.proxmox.com%2Fshow_bug.cgi%3Fid%3D5076>
Please let me know if there are any specific testing scenarios you would
like me to focus on.
Thank you for your excellent work.
Best regards,
Windy
Tested-by: me@doublemine.me
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-08-21 9:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.219.1755767263.385.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=me@doublemine.me \
/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