In article <19a85912-f444-6d2d-d09c-427843307...@gmx.com>,
Kamil Rytarowski wrote:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>On 27.04.2018 21:11, Christos Zoulas wrote:
>> In article ,
>> Kamil Rytarowski wrote:
>>> -=-=-=-=-=-
>>> -=-=-=-=-=-
>>>
>>> I propose to remove e_trapsignal from the compat framewo
On 27.04.2018 21:11, Christos Zoulas wrote:
> In article ,
> Kamil Rytarowski wrote:
>> -=-=-=-=-=-
>> -=-=-=-=-=-
>>
>> I propose to remove e_trapsignal from the compat framework
>>
>> Rationale:
>> - It's currently unused. It was used for Darwin compat.
>> - It's certainly broken and not used i
In article ,
Kamil Rytarowski wrote:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>I propose to remove e_trapsignal from the compat framework
>
>Rationale:
> - It's currently unused. It was used for Darwin compat.
> - It's certainly broken and not used in part of the code where it could
>be used, generating a tra
On 26 April 2018 at 11:26, Manuel Bouyer wrote:
> On Thu, Apr 26, 2018 at 11:20:22AM -0400, Andrew Cagney wrote:
>> > I tested on a olimex lime2 (A20 with a realtek Gbe PHY), it doens't make a
>> > difference either.
>>
>> Unfortunately, it didn't seem to help my 100mb connection.
>> If there's so
I propose to remove e_trapsignal from the compat framework
Rationale:
- It's currently unused. It was used for Darwin compat.
- It's certainly broken and not used in part of the code where it could
be used, generating a trap signal.
- Maintaining debugging features in the compat framework is no
