Re: svn commit: r1850745 - /httpd/httpd/trunk/modules/filters/config.m4

[William A Rowe Jr]

On Tue, Jan 15, 2019 at 8:37 AM Jim Jagielski  wrote:

>
> > On Jan 15, 2019, at 9:21 AM, Eric Covener  wrote:
> >
> > On Tue, Jan 15, 2019 at 9:14 AM Jim Jagielski  wrote:
> >>
> >> On Jan 9, 2019, at 7:41 PM, William A Rowe Jr 
> wrote:
> >>
> >> Hi Jim,
> >>
> >> Does CFLAGS -std=c99 solve your issue? It seems to work here. I'm
> building on the Fedora 29, largely frozen end-of-july. Reverting the patch
> below and toggling -std=c89 to -std=c99 in configure.in building all but
> two modules from trunk is building clean, and results in this command for
> error checking;
> >> /usr/lib64/apr-1/build/libtool --silent --mode=compile gcc  -pthread
> -std=c99 -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes
> -Wmissing-declarations -Wdeclaration-after-statement -Wpointer-arith
> -Wformat -Wformat-security -Wunused -DLINUX -D_REENTRANT -D_GNU_SOURCE
> -DAP_DEBUG
> >>
> >> Is it reasonable to enforce c99 limitations at this late date? I'm not
> suggesting we change the general builds from c89 in the 2.4 branch, but
> that is something we might want to consider for trunk, 20 years out.
> >>
> >>
> >> Personally, I'd be fine allowing c99 in both 2.4 and trunk, considering
> that we are in 2019 already :)
> >>
> >> Any platform that lacks a c99 compatible CC likely doesn't build anyway.
> >
> > As a binary distributor, even though a C99 compiler may be available
> > on platform X, it might not be in use.  Wouldn't love seeing it in
> > 2.4.
>
> I'm not proposing a change for 2.4... but I wouldn't oppose it either :)
>
> Allowing c99 for trunk would make backporting to 2.4 (which would stay
> c89) possibly more difficult. This is either a good thing or a bad thing.
> So far, however, iirc we have not had any issues sticking with c89 and I
> don't think the above would warrant such a change. IMO of course.


I might not have been clear, above. I'm not suggesting changing things for
the
customary build, leave that (at least on httpd 2.4) as -std=c89. I think we
should
have this discussion of when we will begin accepting c99 source patches, but
that isn't the immediate problem you've tripped over.

I see several options;

  Only for maintainer mode, where we are strictly handling all errors,
always
  accept all -std=c99 behaviors (fix any legacy pre-c99 issues that may
arise.)
  All the system headers using c99 (or earlier) semantics should behave
well.

  Or, for maintainer mode, always relax the comments restriction only so we
  have -std=c89 -Werror -Wall -Wno-error=comment (but not modified in the
  modules/filters/config.m4 where it isn't apparent who toggled this.) You
can
  almost call this c99-lite which solves one c99'ism in newer system headers
  without allowing all the c99'isms in system headers.

  Or, staying closest to the proposed patch, add -Wno-error=comment only
  to mod_proxy_html's CPPFLAGS, and stop messing with the rest of the
  compilation for a single module.

In every case, I'm expecting we still adhere to c89, especially in httpd-2.4
branch. A typical compilation (non-maintainer-mode) should catch most
of those irregularities.

Re: svn commit: r1851177 - /httpd/httpd/trunk/docs/manual/mod/mod_cache.xml.fr

[Mario Colindres]

I think that  the wholesome GOOD of this prof will remain a SafeArea here.

On Jan 12, 2019 7:40 AM,  wrote:

Author: lgentis
Date: Sat Jan 12 15:40:57 2019
New Revision: 1851177

URL: http://svn.apache.org/viewvc?rev=1851177=rev
Log:
XML fr doc update.

Modified:
httpd/httpd/trunk/docs/manual/mod/mod_cache.xml.fr

Modified: httpd/httpd/trunk/docs/manual/mod/mod_cache.xml.fr
URL:
http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_cache.xml.fr?rev=1851177=1851176=1851177=diff
==
--- httpd/httpd/trunk/docs/manual/mod/mod_cache.xml.fr [utf-8] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_cache.xml.fr [utf-8] Sat Jan 12
15:40:57 2019
@@ -1,7 +1,7 @@
 
 
 
-
+
 
 

Re: [NOTICE] Intent to T 2.4.28

[William A Rowe Jr]

On Tue, Jan 15, 2019 at 8:16 AM Jim Jagielski  wrote:

> Could I please get one more vote on adding in mod_socache_redis from
> trunk...
>

This suggests one more adopter/reviewer. Has anyone in the community
been using this module and can vouch for it? Anyone is welcome to share
your votes here at dev@ on anything in the STATUS review file, whether
you are a committer or not.

https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/STATUS

If there are no users interested, adopting the responsibility of
maintaining
this seems unwise.

[ANNOUNCE] Apache Roadshow Chicago, Call for Presentations

[Trevor Grant]

Hello Devs!


You're receiving this email because you are subscribed to one or more
Apache developer email lists.

I’m writing to let you know about an exciting event coming to the Chicago
area: The Apache Roadshow Chicago.  It will be held May 13th and 14th at
three bars in the Logan Square neighborhood (Revolution Brewing, The
Native, and the Radler).

There will be six tracks:

   -

   Apache in Adtech:  Tell us how Apache works in your advertising stack
   -

   Apache in Fintech: Tell us how Apache works in your finance/insurance
   business
   -

   Apache in Startups: Tell us how you’re using Apache in your startup
   -

   Diversity in Apache: How do we increase and encourage diversity in
   Apache and tech fields overall?
   -

   Made in Chicago: Apache related things made by people in Chicago that
   don’t fall into other buckets
   -

   Project Shark Tank: Do you want more developers or users for your Apache
   project? Come here and pitch it!


This is an exciting chance to learn about how Apache Projects are in use in
production around Chicago, how business users make the decision to use
Apache projects, to learn about exciting new projects that want help from
developers like you, and how/why to increase diversity in tech and IT.

If you have any use cases of Apache products in Adtech, Fintech, or
Startups; if you represent a minority working in tech and have perspectives
to share, if you live in the Chicagoland area and want to highlight some
work you’ve done on an Apache project, or if you want to get other people
excited to come work on your project, then please submit a CFP before the
deadline on February 15th!

Tickets to the Apache Roadshow Chicago are $100; speakers will get a
complimentary ticket.

We’re looking forward to reading your submissions and seeing you there on
May 13-14!

Sincerely,

Trevor Grant

https://www.apachecon.com/chiroadshow19/cfp.html

https://www.apachecon.com/chiroadshow19/register.html

[ANNOUNCE] Apache Roadshow Chicago, Call for Presentations

[Trevor Grant]

Hello Devs!


You're receiving this email because you are subscribed to one or more
Apache developer email lists.

I’m writing to let you know about an exciting event coming to the Chicago
area: The Apache Roadshow Chicago.  It will be held May 13th and 14th at
three bars in the Logan Square neighborhood (Revolution Brewing, The
Native, and the Radler).

There will be six tracks:

   -

   Apache in Adtech:  Tell us how Apache works in your advertising stack
   -

   Apache in Fintech: Tell us how Apache works in your finance/insurance
   business
   -

   Apache in Startups: Tell us how you’re using Apache in your startup
   -

   Diversity in Apache: How do we increase and encourage diversity in
   Apache and tech fields overall?
   -

   Made in Chicago: Apache related things made by people in Chicago that
   don’t fall into other buckets
   -

   Project Shark Tank: Do you want more developers or users for your Apache
   project? Come here and pitch it!


This is an exciting chance to learn about how Apache Projects are in use in
production around Chicago, how business users make the decision to use
Apache projects, to learn about exciting new projects that want help from
developers like you, and how/why to increase diversity in tech and IT.

If you have any use cases of Apache products in Adtech, Fintech, or
Startups; if you represent a minority working in tech and have perspectives
to share, if you live in the Chicagoland area and want to highlight some
work you’ve done on an Apache project, or if you want to get other people
excited to come work on your project, then please submit a CFP before the
deadline on February 15th!

Tickets to the Apache Roadshow Chicago are $100; speakers will get a
complimentary ticket.

We’re looking forward to reading your submissions and seeing you there on
May 13-14!

Sincerely,

Trevor Grant

https://www.apachecon.com/chiroadshow19/cfp.html

https://www.apachecon.com/chiroadshow19/register.html

[ANNOUNCE] Apache Roadshow Chicago, Call for Presentations

[Trevor Grant]

Hello Devs!


You're receiving this email because you are subscribed to one or more
Apache developer email lists.

I’m writing to let you know about an exciting event coming to the Chicago
area: The Apache Roadshow Chicago.  It will be held May 13th and 14th at
three bars in the Logan Square neighborhood (Revolution Brewing, The
Native, and the Radler).

There will be six tracks:

   -

   Apache in Adtech:  Tell us how Apache works in your advertising stack
   -

   Apache in Fintech: Tell us how Apache works in your finance/insurance
   business
   -

   Apache in Startups: Tell us how you’re using Apache in your startup
   -

   Diversity in Apache: How do we increase and encourage diversity in
   Apache and tech fields overall?
   -

   Made in Chicago: Apache related things made by people in Chicago that
   don’t fall into other buckets
   -

   Project Shark Tank: Do you want more developers or users for your Apache
   project? Come here and pitch it!


This is an exciting chance to learn about how Apache Projects are in use in
production around Chicago, how business users make the decision to use
Apache projects, to learn about exciting new projects that want help from
developers like you, and how/why to increase diversity in tech and IT.

If you have any use cases of Apache products in Adtech, Fintech, or
Startups; if you represent a minority working in tech and have perspectives
to share, if you live in the Chicagoland area and want to highlight some
work you’ve done on an Apache project, or if you want to get other people
excited to come work on your project, then please submit a CFP before the
deadline on February 15th!

Tickets to the Apache Roadshow Chicago are $100; speakers will get a
complimentary ticket.

We’re looking forward to reading your submissions and seeing you there on
May 13-14!

Sincerely,

Trevor Grant

https://www.apachecon.com/chiroadshow19/cfp.html

https://www.apachecon.com/chiroadshow19/register.html

[ANNOUNCE] Apache Roadshow Chicago, Call for Presentations

[Trevor Grant]

Hello Devs!


You're receiving this email because you are subscribed to one or more
Apache developer email lists.

I’m writing to let you know about an exciting event coming to the Chicago
area: The Apache Roadshow Chicago.  It will be held May 13th and 14th at
three bars in the Logan Square neighborhood (Revolution Brewing, The
Native, and the Radler).

There will be six tracks:

   -

   Apache in Adtech:  Tell us how Apache works in your advertising stack
   -

   Apache in Fintech: Tell us how Apache works in your finance/insurance
   business
   -

   Apache in Startups: Tell us how you’re using Apache in your startup
   -

   Diversity in Apache: How do we increase and encourage diversity in
   Apache and tech fields overall?
   -

   Made in Chicago: Apache related things made by people in Chicago that
   don’t fall into other buckets
   -

   Project Shark Tank: Do you want more developers or users for your Apache
   project? Come here and pitch it!


This is an exciting chance to learn about how Apache Projects are in use in
production around Chicago, how business users make the decision to use
Apache projects, to learn about exciting new projects that want help from
developers like you, and how/why to increase diversity in tech and IT.

If you have any use cases of Apache products in Adtech, Fintech, or
Startups; if you represent a minority working in tech and have perspectives
to share, if you live in the Chicagoland area and want to highlight some
work you’ve done on an Apache project, or if you want to get other people
excited to come work on your project, then please submit a CFP before the
deadline on February 15th!

Tickets to the Apache Roadshow Chicago are $100; speakers will get a
complimentary ticket.

We’re looking forward to reading your submissions and seeing you there on
May 13-14!

Sincerely,

Trevor Grant

https://www.apachecon.com/chiroadshow19/cfp.html

https://www.apachecon.com/chiroadshow19/register.html

Re: svn commit: r1850745 - /httpd/httpd/trunk/modules/filters/config.m4

[Jim Jagielski]

> On Jan 15, 2019, at 9:21 AM, Eric Covener  wrote:
> 
> On Tue, Jan 15, 2019 at 9:14 AM Jim Jagielski  wrote:
>> 
>> 
>> 
>> On Jan 9, 2019, at 7:41 PM, William A Rowe Jr  wrote:
>> 
>> Hi Jim,
>> 
>> Does CFLAGS -std=c99 solve your issue? It seems to work here. I'm building 
>> on the Fedora 29, largely frozen end-of-july. Reverting the patch below and 
>> toggling -std=c89 to -std=c99 in configure.in building all but two modules 
>> from trunk is building clean, and results in this command for error checking;
>> /usr/lib64/apr-1/build/libtool --silent --mode=compile gcc  -pthread 
>> -std=c99 -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes 
>> -Wmissing-declarations -Wdeclaration-after-statement -Wpointer-arith 
>> -Wformat -Wformat-security -Wunused -DLINUX -D_REENTRANT -D_GNU_SOURCE 
>> -DAP_DEBUG
>> 
>> Is it reasonable to enforce c99 limitations at this late date? I'm not 
>> suggesting we change the general builds from c89 in the 2.4 branch, but that 
>> is something we might want to consider for trunk, 20 years out.
>> 
>> 
>> Personally, I'd be fine allowing c99 in both 2.4 and trunk, considering that 
>> we are in 2019 already :)
>> 
>> Any platform that lacks a c99 compatible CC likely doesn't build anyway.
> 
> As a binary distributor, even though a C99 compiler may be available
> on platform X, it might not be in use.  Wouldn't love seeing it in
> 2.4.

I'm not proposing a change for 2.4... but I wouldn't oppose it either :)

Allowing c99 for trunk would make backporting to 2.4 (which would stay c89) 
possibly more difficult. This is either a good thing or a bad thing. So far, 
however, iirc we have not had any issues sticking with c89 and I don't think 
the above would warrant such a change. IMO of course.

Re: svn commit: r1850745 - /httpd/httpd/trunk/modules/filters/config.m4

[Eric Covener]

On Tue, Jan 15, 2019 at 9:14 AM Jim Jagielski  wrote:
>
>
>
> On Jan 9, 2019, at 7:41 PM, William A Rowe Jr  wrote:
>
> Hi Jim,
>
> Does CFLAGS -std=c99 solve your issue? It seems to work here. I'm building on 
> the Fedora 29, largely frozen end-of-july. Reverting the patch below and 
> toggling -std=c89 to -std=c99 in configure.in building all but two modules 
> from trunk is building clean, and results in this command for error checking;
> /usr/lib64/apr-1/build/libtool --silent --mode=compile gcc  -pthread -std=c99 
> -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations 
> -Wdeclaration-after-statement -Wpointer-arith -Wformat -Wformat-security 
> -Wunused -DLINUX -D_REENTRANT -D_GNU_SOURCE -DAP_DEBUG
>
> Is it reasonable to enforce c99 limitations at this late date? I'm not 
> suggesting we change the general builds from c89 in the 2.4 branch, but that 
> is something we might want to consider for trunk, 20 years out.
>
>
> Personally, I'd be fine allowing c99 in both 2.4 and trunk, considering that 
> we are in 2019 already :)
>
> Any platform that lacks a c99 compatible CC likely doesn't build anyway.

As a binary distributor, even though a C99 compiler may be available
on platform X, it might not be in use.  Wouldn't love seeing it in
2.4.

Re: svn commit: r1850745 - /httpd/httpd/trunk/modules/filters/config.m4

[Dennis Clarke]

On 1/15/19 9:13 AM, Jim Jagielski wrote:
On Jan 9, 2019, at 7:41 PM, William A Rowe Jr > wrote:


Personally, I'd be fine allowing c99 in both 2.4 and trunk, considering 
that we are in 2019 already :)


Any platform that lacks a c99 compatible CC likely doesn't build anyway.


Any platform that lacks C99 should be ignored. Merely my opinion. Even
worse would be compilers that can not implement C99.

Dennis

Re: [NOTICE] Intent to T 2.4.28

[Jim Jagielski]

Could I please get one more vote on adding in mod_socache_redis from trunk...

It's been waiting for several releases by now.

> On Jan 15, 2019, at 7:27 AM, Daniel Ruggeri  wrote:
> 
> Hi, all;
> It's been a while since we've rolled a release and we've had some recent 
> movement, so I'd like to propose T of 2.4.38 in the next day or two. I'll 
> plan to proceed Thursday morning (US Central).
> -- 
> Daniel Ruggeri

Re: svn commit: r1850745 - /httpd/httpd/trunk/modules/filters/config.m4

[Jim Jagielski]

> On Jan 9, 2019, at 7:41 PM, William A Rowe Jr  wrote:
> 
> Hi Jim,
> 
> Does CFLAGS -std=c99 solve your issue? It seems to work here. I'm building on 
> the Fedora 29, largely frozen end-of-july. Reverting the patch below and 
> toggling -std=c89 to -std=c99 in configure.in  building 
> all but two modules from trunk is building clean, and results in this command 
> for error checking;
> /usr/lib64/apr-1/build/libtool --silent --mode=compile gcc  -pthread -std=c99 
> -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations 
> -Wdeclaration-after-statement -Wpointer-arith -Wformat -Wformat-security 
> -Wunused -DLINUX -D_REENTRANT -D_GNU_SOURCE -DAP_DEBUG
> 
> Is it reasonable to enforce c99 limitations at this late date? I'm not 
> suggesting we change the general builds from c89 in the 2.4 branch, but that 
> is something we might want to consider for trunk, 20 years out.

Personally, I'd be fine allowing c99 in both 2.4 and trunk, considering that we 
are in 2019 already :)

Any platform that lacks a c99 compatible CC likely doesn't build anyway.

[NOTICE] Intent to T 2.4.28

[Daniel Ruggeri]

Hi, all;
   It's been a while since we've rolled a release and we've had some recent 
movement, so I'd like to propose T of 2.4.38 in the next day or two. I'll 
plan to proceed Thursday morning (US Central).
-- 
Daniel Ruggeri