On 08/18/2016 04:11 AM, Yann Ylavic wrote:
On Wed, Aug 17, 2016 at 7:08 PM, Jacob Champion wrote:
What's the procedure for dealing with this in STATUS when I propose
something? A 2.4.x patch hosted... somewhere?
Yes, you can propose a branch merge in a standalone patch, and give a
link to it
On Wed, Aug 17, 2016 at 7:08 PM, Jacob Champion wrote:
>
> What's the procedure for dealing with this in STATUS when I propose
> something? A 2.4.x patch hosted... somewhere?
Yes, you can propose a branch merge in a standalone patch, and give a
link to it in a "2.4.x patch: ..." line (otherwise,
> -Original Message-
> From: Jacob Champion [mailto:champio...@gmail.com]
> Sent: Mittwoch, 17. August 2016 19:09
> To: dev@httpd.apache.org
> Subject: Re: svn commit: r1756556 - /httpd/httpd/branches/2.4.x/STATUS
>
> On 08/16/2016 03:29 PM, yla...@apache.org wrot
On 08/16/2016 03:29 PM, yla...@apache.org wrote:
*) autoconf: minor cleanup and removal of some dead code.
trunk patch: http://svn.apache.org/r1753315
http://svn.apache.org/r1753316
+1: jchampion
+ ylavic: some conflicts with r1753315 in 2.4.x's configure.in.
