On 12/21/2017 01:07 PM, Programmingkid wrote:
On Dec 21, 2017, at 1:40 PM, Eric Blake wrote:
On 12/21/2017 12:36 PM, Programmingkid wrote:
On Dec 21, 2017, at 1:30 PM, Eric Blake wrote:
On 12/21/2017 08:31 AM, Programmingkid wrote:
Now would be a good time to push the strnlen patch.
No
> On Dec 21, 2017, at 1:40 PM, Eric Blake wrote:
>
> On 12/21/2017 12:36 PM, Programmingkid wrote:
>>> On Dec 21, 2017, at 1:30 PM, Eric Blake wrote:
>>>
>>> On 12/21/2017 08:31 AM, Programmingkid wrote:
Now would be a good time to push the strnlen patch.
>>>
>>> No links to the patch? G
On 12/21/2017 12:36 PM, Programmingkid wrote:
On Dec 21, 2017, at 1:30 PM, Eric Blake wrote:
On 12/21/2017 08:31 AM, Programmingkid wrote:
Now would be a good time to push the strnlen patch.
No links to the patch? Generally, when pinging a patch, it's best to reply to
the existing thread,
> On Dec 21, 2017, at 1:30 PM, Eric Blake wrote:
>
> On 12/21/2017 08:31 AM, Programmingkid wrote:
>> Now would be a good time to push the strnlen patch.
>
> No links to the patch? Generally, when pinging a patch, it's best to reply to
> the existing thread, or at least provide a URL to the th
On 12/21/2017 08:31 AM, Programmingkid wrote:
Now would be a good time to push the strnlen patch.
No links to the patch? Generally, when pinging a patch, it's best to
reply to the existing thread, or at least provide a URL to the thread,
where the patch was proposed.
--
Eric Blake, Principa
Now would be a good time to push the strnlen patch.
