codehaus


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: svn commit: r1849177 - /httpd/httpd/trunk/CHANGES


Le 18/12/2018 à 14:58, icing@xxxxxxxxxx a écrit :
Author: icing
Date: Tue Dec 18 13:58:31 2018
New Revision: 1849177

URL: http://svn.apache.org/viewvc?rev=1849177&view=rev
Log:
Update after backport of r1849174 r1849174


Modified:
     httpd/httpd/trunk/CHANGES

Modified: httpd/httpd/trunk/CHANGES
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/CHANGES?rev=1849177&r1=1849176&r2=1849177&view=diff
==============================================================================
--- httpd/httpd/trunk/CHANGES [utf-8] (original)
+++ httpd/httpd/trunk/CHANGES [utf-8] Tue Dec 18 13:58:31 2018
@@ -1,9 +1,6 @@
                                                           -*- coding: utf-8 -*-
  Changes with Apache 2.5.1
- *) mod_md: incorrect behaviour when synchronizing ongoing ACME challenges
-     have been fixed. [Michael Kaufmann, Stefan Eissing]
-
    *) core: Incorrect values for environment variables are substituted when
       multiple environment variables are specified in a directive. [Hank Ibell]

Hi,

I thought that now that 2.5.0 has been tagged, the history of 2.5.0+ should not be axed when backported (i.e. this change would be in 2.5.1, but is not in 2.5.0, which is tagged, so "does exist")

Should this kind of commit be reverted?

CJ