Re: Bugs in apr_file_trunc

2017-06-30 Thread William A Rowe Jr
On Fri, Jun 30, 2017 at 1:24 PM, Ivan Zhakov wrote: > On 30 June 2017 at 19:46, Nick Kew wrote: >> On Fri, 2017-06-30 at 11:44 -0400, Jim Jagielski wrote: >>> Thx... it's a shame that either (1) these bugs aren't reported >>> to the APR dev team to fix or (2) that they are, but that the >>> dev t

Re: Bugs in apr_file_trunc

2017-06-30 Thread Jim Jagielski
Thx. Committed revision 1800458 for 1.6.x > On Jun 30, 2017, at 2:24 PM, Ivan Zhakov wrote: > > 1788929

Re: Bugs in apr_file_trunc

2017-06-30 Thread Ivan Zhakov
On 30 June 2017 at 19:46, Nick Kew wrote: > On Fri, 2017-06-30 at 11:44 -0400, Jim Jagielski wrote: >> Thx... it's a shame that either (1) these bugs aren't reported >> to the APR dev team to fix or (2) that they are, but that the >> dev team isn't aware or following up. > > Well, there may or may

Re: Bugs in apr_file_trunc

2017-06-30 Thread Nick Kew
On Fri, 2017-06-30 at 11:44 -0400, Jim Jagielski wrote: > Thx... it's a shame that either (1) these bugs aren't reported > to the APR dev team to fix or (2) that they are, but that the > dev team isn't aware or following up. Well, there may or may not be some report deep in the archives or in bugz

Re: Bugs in apr_file_trunc

2017-06-30 Thread Jim Jagielski
Thx... it's a shame that either (1) these bugs aren't reported to the APR dev team to fix or (2) that they are, but that the dev team isn't aware or following up. Either alternative is sad. > On Jun 30, 2017, at 10:49 AM, Julian Foad wrote: > > It came to my notice that apr_file_trunc() has som