Jay Satiro
Jay Satiro
IMO this isn't a bug, it's either an enhancement or a feature request. The user wants an easier way to tell autotools to build curl with Windows Unicode support, like...
I've rebased your branch on upstream/master. Regarding the last commit I don't understand what it fixes. Can you please add a commit message that explains why it is necessary? I...
> I know what is the problem, I know it's a server issue, but Curl can get through with the right ssl parameter, parameter that Curl has not at the...
See #10430 for my take on this, which is calling getsockopt directly without caching, and then reset FD_WRITE only if TCP. It's unclear to me if extra user fd's that...
I have a branch where I made some changes to ignore the specific TCF1 hardware ID. Try https://github.com/doublerebel/nvram-cfg-parser/compare/master...jay:enhancement_hwid see if helps. I never submitted it as a PR. The last...
> thanks. did you also implement this change too? > > [ilium007@cdf6e55](https://github.com/ilium007/nvram-cfg-parser/commit/cdf6e550f7cf906d192b3f1910645428d01b444a) I use a branch https://github.com/doublerebel/nvram-cfg-parser/compare/master...jay:working which contains that fix as well as https://github.com/doublerebel/nvram-cfg-parser/compare/master...jay:enhancement_hwid and https://github.com/doublerebel/nvram-cfg-parser/compare/master...jay:fix_parsing_skipping_some_pairs and https://github.com/doublerebel/nvram-cfg-parser/compare/master...jay:enhancement_sort_json but...
prepending `\\?\` to a path disables all parsing of the path. like any forward slashes and .. will not be converted. you are assuming that any path starting with the...
> that modified path is only passed into _open and _wopen I agree but I'm saying the logic is wrong. You can't assume that if a user specifies a path...
> Right, it disables the path parsing, but it does not matter, the limitation `PATH_MAX` breaks the file opening before the parse result that can be less than `PATH_MAX`. Hence,...