- wine-gitlab - winehq.org

Re: [PATCH v2 0/2] MR5229: ole32: Do not lock storage in read-only deny-write mode. - approved
by Alexandre Julliard (＠julliard) 05 Mar '24

05 Mar '24

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5229

1 0

Re: [PATCH v3 0/6] MR5171: wined3d/nvrc: Move state application to nvrc_apply_draw_state(). - approved
by Alexandre Julliard (＠julliard) 05 Mar '24

05 Mar '24

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5171

1 0

Re: [PATCH v2 0/1] MR5235: arm64: Expose information about more modern CPU extensions - approved
by Alexandre Julliard (＠julliard) 05 Mar '24

05 Mar '24

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5235

1 0

Re: [PATCH v4 0/6] MR5193: mouhid, win32u: Send and receive WM_POINTER messages. - approved
by Alexandre Julliard (＠julliard) 05 Mar '24

05 Mar '24

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5193

1 0

Re: [PATCH v2 0/5] MR5233: Dbghelp and debug info lookup (Part II) - approved
by Alexandre Julliard (＠julliard) 05 Mar '24

05 Mar '24

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5233

1 0

Re: [PATCH v2 0/1] MR5227: ntdll: Respect red zone in usr1_handler() on x64. - approved
by Alexandre Julliard (＠julliard) 05 Mar '24

05 Mar '24

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5227

1 0

[PATCH 0/2] MR5226: d3d10_1/tests: Add a basic test for returned preferred profiles.
by Nikolay Sivov (＠nsivov) 05 Mar '24

05 Mar '24

Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5226

3 3

Re: [PATCH v6 0/4] MR5161: d3drm: Implement Update and related functions
by Zebediah Figura (＠zfigura) 05 Mar '24

05 Mar '24

On Tue Mar 5 20:50:52 2024 +0000, Jeffrey Smith wrote: > As the documentation states that the updated region _may_ be larger than > the specified region, this seemed safer. Yeah, but I don't really want to trust that programs are following the letter of the documentation either, especially with an API this old. I'd rather at least test exact values, even if we have to mark them todo. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5161#note_63598

1 0

Re: [PATCH v6 0/4] MR5161: d3drm: Implement Update and related functions
by Jeffrey Smith (＠whydoubt) 05 Mar '24

05 Mar '24

On Tue Mar 5 19:10:38 2024 +0000, Zebediah Figura wrote: > Any reason not to test the exact values? As the documentation states that the updated region _may_ be larger than the specified region, this seemed safer. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5161#note_63597

1 0

Re: [PATCH v6 0/4] MR5161: d3drm: Implement Update and related functions
by Jeffrey Smith (＠whydoubt) 05 Mar '24

05 Mar '24

On Tue Mar 5 19:10:37 2024 +0000, Zebediah Figura wrote: > Can there be multiple updates? You mention the possibility of "at least" > one update in your tests; should we be storing an array instead? Multiple calls to ForceUpdate seem entirely reasonable. This was part of trying to keep things simple for the implementation and effectively have a single dirty-rectange. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5161#note_63596

1 0

2025

2024

2023

2022

wine-gitlab