Subject: Re: [PATCH] ares_parse_txt_reply: add `record_start` field

Re: [PATCH] ares_parse_txt_reply: add `record_start` field

From: Fedor Indutny <fedor_at_indutny.com>
Date: Fri, 5 Dec 2014 02:40:05 +0400

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 <daniel_at_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
>

Received on 2014-12-04