Re: [Mingw-w64-public] [PATCH] Use LPCVOID instead of 'const LPVOID' for VerQueryValue

2017-03-20 Thread NightStrike
On Mon, Mar 20, 2017 at 9:42 PM, David Wohlferd wrote: > >> I don't think application/octet-stream is something we would want to >> enable. Doesn't that sound like something that would be abused? > > I suppose application/octet-stream might be useful if we commonly worked > with binary files for

Re: [Mingw-w64-public] [PATCH] Use LPCVOID instead of 'const LPVOID' for VerQueryValue

2017-03-20 Thread David Wohlferd
> I don't think application/octet-stream is something we would want to > enable. Doesn't that sound like something that would be abused? I suppose application/octet-stream might be useful if we commonly worked with binary files for patches. But I agree with you, don't do it. A google search t

Re: [Mingw-w64-public] [PATCH] Use LPCVOID instead of 'const LPVOID' for VerQueryValue

2017-03-20 Thread NightStrike
On Mon, Mar 20, 2017 at 9:34 AM, Mateusz Mikuła wrote: > It explains why my patches created with `git format-patch` couldn't > make it. > > Their mime type is `text/x-diff`. I added text/x-diff to the list. Give it a shot. ---

Re: [Mingw-w64-public] [PATCH] Use LPCVOID instead of 'const LPVOID' for VerQueryValue

2017-03-20 Thread NightStrike
On Mon, Mar 20, 2017 at 9:23 AM, David Grayson wrote: > Oops, that was the problem then. It was "application/octet-stream" because > I was constructing the email with the Ruby "mail" gem that doesn't > recognize ".patch" files as being text. I'll use better methods in the > future. I don't thin

Re: [Mingw-w64-public] [PATCH] Use LPCVOID instead of 'const LPVOID' for VerQueryValue

2017-03-20 Thread Mateusz Mikuła
I checked it with `file --mime-type something.patch` in MSYS2 shell; something.patch was generated by git. -- Original Message -- Subject: Re: [Mingw-w64-public] [PATCH] Use LPCVOID instead of 'const LPVOID' for VerQueryValue Date: Mon, 20 Mar 2017 23:15:21 +0800 To: Mingw-w64-public Fr

Re: [Mingw-w64-public] [PATCH] Use LPCVOID instead of 'const LPVOID' for VerQueryValue

2017-03-20 Thread Liu Hao
On 2017/3/20 22:34, Mateusz Mikuła wrote: > It explains why my patches created with `git format-patch` couldn't > make it. > > Their mime type is `text/x-diff`. Isn't it our mail clients that guess MIME types of attachments? The diff file doesn't have any MIME type information stored with it. --

Re: [Mingw-w64-public] [PATCH] Use LPCVOID instead of 'const LPVOID' for VerQueryValue

2017-03-20 Thread Mateusz Mikuła
It explains why my patches created with `git format-patch` couldn't make it. Their mime type is `text/x-diff`. -- Original Message -- Subject: Re: [Mingw-w64-public] [PATCH] Use LPCVOID instead of 'const LPVOID' for VerQueryValue Date: Mon, 20 Mar 2017 00:13:44 -0500 To: Mingw-w64-publi

Re: [Mingw-w64-public] [PATCH] Use LPCVOID instead of 'const LPVOID' for VerQueryValue

2017-03-20 Thread David Grayson
Oops, that was the problem then. It was "application/octet-stream" because I was constructing the email with the Ruby "mail" gem that doesn't recognize ".patch" files as being text. I'll use better methods in the future. --David On Sun, Mar 19, 2017 at 10:13 PM, NightStrike wrote: > Do you kn

[Mingw-w64-public] [PATCH] Add DBG_PRINTEXCEPTION_WIDE_C exception

2017-03-20 Thread Jon Turney
Windows 10 now has a separate exception for OutputDebugStringW, rather than converting the string to ANSI and raising DBG_PRINTEXCEPTION_C. (See https://ntquery.wordpress.com/2015/09/07/windows-10-new-anti-debug-outputdebugstringw/) Signed-off-by: Jon Turney --- mingw-w64-headers/include/ntsta