You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@apr.apache.org by tr...@apache.org on 2012/08/05 15:29:10 UTC

svn commit: r1369580 - /apr/apr-util/branches/1.5.x/CHANGES

Author: trawick
Date: Sun Aug  5 13:29:10 2012
New Revision: 1369580

URL: http://svn.apache.org/viewvc?rev=1369580&view=rev
Log:
use standard verbage when pointing to the 1.4.x changes file

remove an entry for a fix which was backported to 1.4.x
(now the 1.5.x entries are all 1.5.x-specific)

Modified:
    apr/apr-util/branches/1.5.x/CHANGES

Modified: apr/apr-util/branches/1.5.x/CHANGES
URL: http://svn.apache.org/viewvc/apr/apr-util/branches/1.5.x/CHANGES?rev=1369580&r1=1369579&r2=1369580&view=diff
==============================================================================
--- apr/apr-util/branches/1.5.x/CHANGES [utf-8] (original)
+++ apr/apr-util/branches/1.5.x/CHANGES [utf-8] Sun Aug  5 13:29:10 2012
@@ -3,16 +3,13 @@ Changes with APR-util 1.5.0
 
   *) dbd_pgsql_escape: Use PQescapeStringConn. [Nick Kew]
 
-  *) apr_password_validate: Increase maximum hash string length to allow
-     more than 9999 rounds with sha512-crypt. PR 53410. [Stefan Fritsch]
-
   *) apr_password_validate, apr_bcrypt_encode: Add support for bcrypt encoded
      passwords. The bcrypt implementation uses code from crypt_blowfish
      written by Solar Designer <solar openwall com>. apr_bcrypt_encode creates
      hashes with "$2y$" prefix, but apr_password_validate also accepts the old
      prefix "$2a$". [Stefan Fritsch]
 
-Changes with APR-util 1.4.0
+Changes with APR-util 1.4.x and later:
 
   *) http://svn.apache.org/viewvc/apr/apr-util/branches/1.4.x/CHANGES?view=markup
 



Re: svn commit: r1369580 - /apr/apr-util/branches/1.5.x/CHANGES

Posted by Jeff Trawick <tr...@gmail.com>.
On Sun, Aug 5, 2012 at 9:29 AM,  <tr...@apache.org> wrote:
> Author: trawick
> Date: Sun Aug  5 13:29:10 2012
> New Revision: 1369580
>
> URL: http://svn.apache.org/viewvc?rev=1369580&view=rev
> Log:
> use standard verbage when pointing to the 1.4.x changes file
>
> remove an entry for a fix which was backported to 1.4.x
> (now the 1.5.x entries are all 1.5.x-specific)

sf, this is just stating the obvious, but before rolling apr-util
1.5.0 be sure to add back all the CHANGES entries from unreleased
apr-util 1.4.2 and 1.4.3