[openssl-commits] [web] master update

[Richard Levitte]

The branch master has been updated
  discards  eeb7c341f09ec323bcaaafeee1c56c977565b116 (commit)
       via  a345bc8dd66b5dac2ddc915fe57ba2fafeb3b62a (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (eeb7c341f09ec323bcaaafeee1c56c977565b116)
            \
             N -- N -- N (a345bc8dd66b5dac2ddc915fe57ba2fafeb3b62a)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.


- Log -----------------------------------------------------------------
commit a345bc8dd66b5dac2ddc915fe57ba2fafeb3b62a
Author: Richard Levitte <levitte at openssl.org>
Date:   Thu Mar 29 14:15:27 2018 +0200

    source/: translate /source/openssl-x.y.z*.tar.gz -> /source/old/x.y.z/...
    
    Some people try to access older archive through their original
    position.  Help them along.

-----------------------------------------------------------------------

Summary of changes:
 source/.htaccess | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/.htaccess b/source/.htaccess
index 97cefb5..1bbeac9 100644
--- a/source/.htaccess
+++ b/source/.htaccess
@@ -1,3 +1,3 @@
 RewriteEngine on
 RewriteCond %{REQUEST_FILENAME} !-f
-RewriteRule ^(openssl-(\d+\.\d+\.\d+).*\.tar\.gz)  old/$2/$1 [L,R=301,NC]
+RewriteRule ^(openssl-(\d+\.\d+\.\d+).*\.tar\.gz) /source/old/$2/$1 [L,R=301,NC]