Le 22/06/2016 à 22:49, Christophe JAILLET a écrit :
Le 22/06/2016 à 22:46, Christophe JAILLET a écrit :
Thx,
it seems that mod_proxy_http2 is missing as well.
Docs are also missing in 2.4 branch and should be added before T,
IMHO.
Well, mod_proxy_hcheck.xml exists in 2.4.x, but html files
> -Ursprüngliche Nachricht-
> Von: Christophe JAILLET [mailto:christophe.jail...@wanadoo.fr]
> Gesendet: Mittwoch, 22. Juni 2016 22:47
> An: dev@httpd.apache.org
> Betreff: Re: AW: mod_proxy_hcheck Compoent in bugzilla
>
> Thx,
>
> it seems that mod_proxy_http2 is missing as well.
Le 22/06/2016 à 22:46, Christophe JAILLET a écrit :
Thx,
it seems that mod_proxy_http2 is missing as well.
Docs are also missing in 2.4 branch and should be added before T, IMHO.
Well, mod_proxy_hcheck.xml exists in 2.4.x, but html files seem to be
missing.
CJ
Thx,
it seems that mod_proxy_http2 is missing as well.
Docs are also missing in 2.4 branch and should be added before T, IMHO.
CJ
Le 22/06/2016 à 22:39, Plüm, Rüdiger, Vodafone Group a écrit :
Done.
Regards
Rüdiger
-Ursprüngliche Nachricht-
Von: Christophe JAILLET
Done.
Regards
Rüdiger
> -Ursprüngliche Nachricht-
> Von: Christophe JAILLET [mailto:christophe.jail...@wanadoo.fr]
> Gesendet: Mittwoch, 22. Juni 2016 22:33
> An: dev@httpd.apache.org
> Betreff: mod_proxy_hcheck Compoent in bugzilla
>
> Hi,
>
> as it will be released soon,
Hi,
as it will be released soon, mod_proxy_hcheck should be added to
bugzilla's Components list.
I don't remind who to ask for it, so...
CJ
On Wed, Jun 22, 2016 at 10:20 AM, William A Rowe Jr
wrote:
>
> Attached /was/ a patch, now attached again...
>
This patch solves the 80/20... but I'm seeing something disturbing
comparing the
original to the new logic in the new configure output from buildconf...
something
Subj sez it all... afaict, there are no showstoppers and
no outstanding issues (none seen in STATUS, or noted as
such on any Email threads).
So... anyone opposed to a T tomorrow in the hopes
of getting this out to people by the start of next week??
On Wed, Jun 22, 2016 at 10:19 AM, William A Rowe Jr
wrote:
> On Wed, Jun 22, 2016 at 7:26 AM, William A Rowe Jr
> wrote:
>
>>
>>> Have a look at r1749658 & r1749659 for the simplest solution I could
>> come up with, and let me know what you think?
>>
>
On Wed, Jun 22, 2016 at 7:26 AM, William A Rowe Jr
wrote:
>
>> Have a look at r1749658 & r1749659 for the simplest solution I could
> come up with, and let me know what you think?
>
r1749679 improves this a bit further by explaining to the user why
proxy_hcheck
isn't built
On Tue, Jun 21, 2016 at 2:33 PM, Ruediger Pluem wrote:
>
> On 06/21/2016 05:39 PM, William A Rowe Jr wrote:
> > Just retested on 2.4.x branch, better but still problematic...
>
> Would that suit better (against current 2.4.x):
>
> Index: config.m4
>
My plan is to tag T once we get the configure stuff sorted out.
I am recalling this VOTE as well.
> On Jun 21, 2016, at 10:58 AM, William A Rowe Jr wrote:
>
>
>
> > On Jun 21, 2016, at 7:39 AM, Jim Jagielski wrote:
> >
> > Just a reminder for those still testing and/or waiting to cast
> > a vote: One cannot veto a release and even tho OtherBill has
In an ideal world, we'd have test cases for each bug ever found.
In an ideal world, we'd only call something a regression when we have a test
case for it.
In an ideal world, we'd have tireless testers with infinite time to get things
right.
In an ideal world, we do not have to compromise.
In
15 matches
Mail list logo