OK, I've attached git versions of these patches to this email that I made in Linux according to those instructions. I don't know whether I did this right, since I'm a Windows person who far prefers Subversion. Why does the web site have instructions for the non-git case when that's not the form the mailing list wants?
---- Steve Holme <[email protected]> wrote: > On Mon, 2 Dec 2013, [email protected] wrote: > > > In case something is unusable from the raw email > > text, I've also attached these patch files as file > > attachments. > > Thank you for your help with fixing up some of the warnings in Curl - it is > much appreciated. > > I can't speak for the 1st and 3rd patch as they are outside my realm within > the curl project but I agree with the POP3 change you submitted. Rather than > patch it up as myself, and take credit for it, could you please submit git > patches against the latest version of code in the repository as per the > following link? It will also help the other reviewers here as well as provide > a speedy resolution ;-) > > http://curl.haxx.se/dev/contribute.html#How_To_Make_a_Patch_with_git > > Many thanks again > > Kind Regards > > Steve > ------------------------------------------------------------------- > List admin: http://cool.haxx.se/list/listinfo/curl-library > Etiquette: http://curl.haxx.se/mail/etiquette.html
0001-curl_threads-Fix-Windows-64-bit-pointer-warning.patch
Description: Binary data
0002-pop3-Make-POP3_TYPE_ANY-unsigned-to-fix-warning.patch
Description: Binary data
0003-darwinssl-Fix-if-10.6.0-for-SecKeychainSearch.patch
Description: Binary data
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
