| Message ID | 20250403222139.1317475-3-eblake@redhat.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
Sorry for the typo in the subject line; that should be -rc3 (and not rce - this is not an exploit). On Thu, Apr 03, 2025 at 05:19:26PM -0500, Eric Blake wrote: > The following changes since commit 0adf626718bc0ca9c46550249a76047f8e45da15: > > Update version for v10.0.0-rc2 release (2025-04-01 13:15:45 -0400)
Applied, thanks. Please update the changelog at https://wiki.qemu.org/ChangeLog/10.0 for any user-visible changes.
The following changes since commit 0adf626718bc0ca9c46550249a76047f8e45da15: Update version for v10.0.0-rc2 release (2025-04-01 13:15:45 -0400) are available in the Git repository at: https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2025-04-03 for you to fetch changes up to 961841472d25ab70642d182e486b36afeb3fef26: Revert "iotests: Stop NBD server in test 162 before starting the next one" (2025-04-03 16:57:57 -0500) ---------------------------------------------------------------- NBD patches for 2025-04-03 - revert iotest 162 workaround, now that qemu-nbd bug is fixed ---------------------------------------------------------------- Thomas Huth (1): Revert "iotests: Stop NBD server in test 162 before starting the next one" tests/qemu-iotests/162 | 1 - 1 file changed, 1 deletion(-) Low risk for -rc3 (only affects iotest not main binaries), but that also means that given how close we are to release, it's also okay if it gets delayed if nothing else that actually needs -rc3 surfaces.