On Thu, Aug 10, 2017 at 11:04:10AM -0400, Jeremie Courreges-Anglas wrote:
> On Thu, Aug 10 2017, Florian Obser wrote:
> > On Tue, Aug 08, 2017 at 11:08:14AM +0200, Jeremie Courreges-Anglas wrote:
> >>
> >> So rtadvd has this complex code that tries to parse multiple routing
> >> messages, when it
On Thu, Aug 10 2017, Florian Obser wrote:
> On Tue, Aug 08, 2017 at 11:08:14AM +0200, Jeremie Courreges-Anglas wrote:
>>
>> So rtadvd has this complex code that tries to parse multiple routing
>> messages, when it actually reads only one message at a time from the
>> routing socket. The diff bel
On Tue, Aug 08, 2017 at 11:08:14AM +0200, Jeremie Courreges-Anglas wrote:
>
> So rtadvd has this complex code that tries to parse multiple routing
> messages, when it actually reads only one message at a time from the
> routing socket. The diff below attempts to acknowledge this and tries
> to be
So rtadvd has this complex code that tries to parse multiple routing
messages, when it actually reads only one message at a time from the
routing socket. The diff below attempts to acknowledge this and tries
to be as mechanical as possible, variable renaming/gc'ing can happen
later. Better use c
