--
v2: wined3d: Use unsigned type for res_type bit field.
wined3d: Remove unused parallel_point_count variable.
wined3d: Use return type to return result from read_dword.
https://gitlab.winehq.org/wine/wine/-/merge_requests/4151
Hi,
I just trapped into the same `whitespace` problem. Is there a plan to solve the issue?
Another question - is it a valid workaround to ensure there are no `whitespace only` lines in the bat file?
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/277#note_49569
Previously long URI/URLs (> 1024 characters) would cause a stack corruption and crash Wine. After this MR, Wine will no longer crash but the URL is not opened either primarily due to `SHELL_Argify` limitations.
--
v3: shell32: Increase timeout for long URLs
https://gitlab.winehq.org/wine/wine/-/merge_requests/2383
Sorry, i can't get this to work. Maybe i messed something up in between. now got:
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
Sigh....
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4143#note_49564
> Yeah, but this isn't necessarily about not trusting Windows apps, i.e. malice or malware, but rather that they can't be designed around it (since they assume Windows environment), so they would have privacy issues without even wanting to. At the very least maybe use
Of course Windows apps can be designed around it. In the Windows environment they'd retrieve a real hardware ID that should be handled with the same care.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4108#note_49556
On Sat Oct 21 10:27:59 2023 +0000, Jinoh Kang wrote:
> Okay, I've read the prior discussions regarding the rationale.
> Still, I don't think you should change the System UUID for *existing*
> prefixes. Perhaps we could use the registry to detect whether the
> prefix is new, and use the new algorithm for new prefixes. We could
> also record the UUID in the registry "permanently."
Maintaining any way of backward compat on this ID doesn't look feasible. E. g., the current way with a bug reports bios hashtag in serial field on my desktop due to missing fields not being handled. This ID is already non-unique, and maintaining these algorithms backwards would take unreasonable amount of effort (with arguably no gains). Probably more important, /etc/machine-id can be changed anytime by user or system resintall, it is not true hardware id. If anything firmly relies on HW id to persist forever, it is broken already.
Regarding the original discussion, I also don't really understand why we should necessarily obfuscate /etc/machine-id for uuid / serial reporting. App has access to the file anyway, and Wine neither sends the ID anywhere nor tracks the user, it is between the app and the user. On Windows fwiw it will get real motherboard serial and other information like that.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4108#note_49550