The branch master has been updated
  discards  774bd55145377e4911dae22055eaea454b617325 (commit)
       via  281bb29486558342679d3e928972c306325d0d7c (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 (774bd55145377e4911dae22055eaea454b617325)
            \
             N -- N -- N (281bb29486558342679d3e928972c306325d0d7c)

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 281bb29486558342679d3e928972c306325d0d7c
Author: Richard Levitte <levi...@openssl.org>
Date:   Tue Feb 13 15:45:58 2018 +0100

    Add 1.1.1 stuff

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

Summary of changes:
 bin/mk-newmanpages | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bin/mk-newmanpages b/bin/mk-newmanpages
index 4055f86..975f176 100755
--- a/bin/mk-newmanpages
+++ b/bin/mk-newmanpages
@@ -12,7 +12,7 @@ use Pod::Simple::XHTML;
 
 __PACKAGE__->run(@ARGV);
 
-sub Releases { return (qw(master)); }
+sub Releases { return (qw(1.1.1 master)); }
 sub Sections { return (qw(man1 man3 man5 man7)); }
 
 sub getRelease {
_____
openssl-commits mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-commits

Reply via email to