On 2013-12-28 15:45, Jiri Slachta wrote:
> Hi!
>
>>
>> This "cover-letter" is nice, but 2 of the patches miss a proper
>> changelog - pointing at least to the upstream commit-id.
>> As an example Linux-stable [1].
>> A new uClibc 0.9.33.x is overdue...
>
> So what should I do? Should I wait for
Hi!
>
> This "cover-letter" is nice, but 2 of the patches miss a proper
> changelog - pointing at least to the upstream commit-id.
> As an example Linux-stable [1].
> A new uClibc 0.9.33.x is overdue...
So what should I do? Should I wait for next uClibc release or just resend those
patches with
On Sat, Dec 28, 2013 at 2:51 PM, Jiri Slachta wrote:
> Hello,
>
> please consider three previous patches as a patchset. Those patches were
> backported from uClibc
> master which fixes DNS hangups etc..
>
> The patchset:
> http://patchwork.openwrt.org/patch/4650/
> http://patchwork.openwrt.org/pa
Hello,
please consider three previous patches as a patchset. Those patches were
backported from uClibc
master which fixes DNS hangups etc..
The patchset:
http://patchwork.openwrt.org/patch/4650/
http://patchwork.openwrt.org/patch/4649/
http://patchwork.openwrt.org/patch/4648/
Further details a