On Thu, Jun 9, 2016 at 3:52 PM, Michael Kaufmann
wrote:
>
> Note that "Suppress 'h2' announcements in Upgrade: header" has been
> inserted at the top of the STATUS file; it should probably be moved to the
> bottom of the 'Patches proposed' section.
>
Yea, that would be a problem, it will get no
Zitat von William A Rowe Jr :
Skimming the responses, they just keep getting more and more amusing, and
shining a candle to the absurdity of keeping this non-sequitur request
response.
Could you go ahead and add that conditional?
To all developers who participated in this discussion: Please
Hi all,
It may be too late now that the T&R machinery is in motion, but I'll
bump some of my patchsets:
- APXS: https://bz.apache.org/bugzilla/show_bug.cgi?id=58926
Quality-of-life improvements for users of the APXS tool, as well as some
code cleanup for the script itself.
- DUMP_INCLUDES:
On Tue, Sep 1, 2015 at 2:31 AM, wrote:
> Author: rpluem
> Date: Tue Sep 1 07:31:11 2015
> New Revision: 1700408
>
> URL: http://svn.apache.org/r1700408
> Log:
> * Fix a regression with 2.2.31 that caused inherited workers to
> use a different scoreboard slot then the original one.
> This has
2016-06-08 13:42 GMT+02:00 Luca Toscano :
> [+devs]
>
> 2016-06-07 23:02 GMT+02:00 Luca Toscano :
>
>>
>>
>> 2016-06-07 10:55 GMT+02:00 Vacelet, Manuel :
>>
>>>
>>>
>>> On Mon, Jun 6, 2016 at 5:32 PM, Vacelet, Manuel <
>>> manuel.vace...@enalean.com> wrote:
>>>
dOn Mon, Jun 6, 2016 at 5:00 PM
Could you, when time allows, check if r1747550 in trunk now builds without
problems?
I duplicated the necessary code - for now - into h2_proxy_util.c. While I think
that
parts of it should migrate to core, I do not want to introduce new APIs right
now.
With duplication, we have all options stil
Ah, should read my inbox to the end. Thanks William for straightening this out.
-Stefan
> Am 09.06.2016 um 09:54 schrieb Stefan Eissing :
>
>
>> Am 08.06.2016 um 15:22 schrieb Jim Jagielski :
>>
>>> It is just a remark that we should move forward and either backport
>>> ap_cstr_casecmp[n] or
> Am 08.06.2016 um 15:22 schrieb Jim Jagielski :
>
>> It is just a remark that we should move forward and either backport
>> ap_cstr_casecmp[n] or decide to delay it to another release.
>
> I'd really prefer that it be added to this release... But I also
> know that there's some overlap w/ APR