Hello Daniel! The patch was in the first email from this thread. Let me re-paste it here just in case.
Regarding node.js - yeah, users asked us to fix the TXT replies and we waited for c-ares upstream to land the patch, but since it didn't happen - we floated the patch on our own. I don't say that c-ares is causing any problems, it is ourselves causing problems on us :) However I'd still be very pleased if you'll land this patch or help me get it into upstream. Thank you, Fedor. On Fri, Dec 5, 2014 at 12:59 AM, Daniel Stenberg <dan...@haxx.se> wrote: > On Thu, 4 Dec 2014, Fedor Indutny wrote: > > I still would like to ask you to land this in the form it has right now. >> > > You'd simplify our lives if you'd also attach the patch you're talking > about, or a link to it! > > This has already caused some problems with incompatibility between c-ares >> in node.js and the distributed shared library. >> > > How so? You mean they went ahead and patched their embedded library > version and then somehow users mix the standard build and their custom > version? > > -- > > / daniel.haxx.se >
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJTNIorAAoJEPsOEJWxeXmZTDAP/0BVAUgror62mPtpTb/VlO+o Y7HFycmhNJxkDMGtuwI1/KTzL4+juTq/7kLteBSyhlbHkxCO2ygYJYV9acNtuj3C Qb7KitslvAHWnzWhtWlfBALI0QOHxz5GIoFWQZcqnvRzHtL6AJLxKC1duEpFsEKW SwNuhCwO6oz3BaKw11L95GVFNacYwH3sdIs3ykUOgSv8itms36KxZI3mdqQdxxv7 o4NEFqcUsMxlPM7IDSHekXJuf6pN7lbxuhU2qllmUHiwz1qNGhGzD5JzNEqjlJNq ggyzD+j8EIXwmZ3R+JaKbdutzIzcioq5MwdxTDqx7TOn7UayRjksXFKwY3vTe0zE 1OtnMdRdS75AVULvaXp/D+ulDrT2Yxp84ScI/EVWaheI8nEXEdN/5DeKkdEGQhtS B+fS0+C6Qc/Z8MiBAVlmXE0AaEk5wZd1eFoMY996iZ4h/aZSoXwg8Wmi8ITOpAjK ApMZMA3evfhO+N0HpRS/++tTnE0pTUcmAYW1rCFtPSxJEnlXdOm/jIYqTIZCYDLF d2goef8gg4MbrOsHu7DKuPjC1+3UXdP3l84qsBlc89by2fvx08cF+YtTfEkYH7Ka 1NSRKJorshTDajziM2bwiUEr3KX6HV661ujUcbIxtNKVC+4nZ3JNYAwzePMyob7a C48VQpBCP0ITQRa+KP3x =9BGU -----END PGP SIGNATURE-----
0001-ares_parse_txt_reply-add-record_start-field.patch
Description: Binary data
