I was hoping that the new tests would provide evidence that RtlQueryRegistryValues uses RegGetValue to ensure that multi-strings are double-null-terminated. Instead the tests suggest that my hypothesis was wrong because RegGetValue only ensures single null termination, not double null termination. We should fix RegGetValue anyway for the sake of applications that expect it to null-terminate.
--
v5: kernelbase: Ensure null termination in RegGetValue[AW].
windowscodecs: Use RegQueryValueExW in ComponentInfo_GetStringValue.
twinapi.appcore: Initialize size argument to RegGetValueW.
shell32: Pass size in bytes to RegGetValueW.
msi: Initialize size argument to GetRegValueW.
mscoree: Pass size in bytes to RegGetValueW.
https://gitlab.winehq.org/wine/wine/-/merge_requests/5969
--
v3: winegstreamer: Respect video format padding for input buffers too.
winegstreamer: Normalize the video processor media types apertures.
winegstreamer: Normalize both input and output media types stride at once.
winegstreamer: Use video info stride in buffer meta rather than videoflip.
winegstreamer: Keep the input caps on the transform.
winegstreamer: Use a new wg_video_buffer_pool class to add buffer meta.
winegstreamer: Only use pool and set buffer meta for raw video frames.
https://gitlab.winehq.org/wine/wine/-/merge_requests/5972