The branch master has been updated
  discards  69298c27369f59c4c1cbb4ee34d141aac9adc09e (commit)
       via  238ca81834d315ce2874eee155d3268e98d92d94 (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 (69298c27369f59c4c1cbb4ee34d141aac9adc09e)
             N -- N -- N (238ca81834d315ce2874eee155d3268e98d92d94)

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 238ca81834d315ce2874eee155d3268e98d92d94
Author: Richard Levitte <>
Date:   Tue Feb 13 15:45:58 2018 +0100

    Add 1.1.1 stuff


Summary of changes:
 docs/manpages.html | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/manpages.html b/docs/manpages.html
index 82f6e7d..91623d9 100644
--- a/docs/manpages.html
+++ b/docs/manpages.html
@@ -14,6 +14,7 @@
               <li><a href="manmaster">master</a></li>
+              <li><a href="man1.1.1">1.1.1 (pre-release)</a></li>
               <li><a href="man1.1.0">1.1.0</a></li>
               <li><a href="man1.0.2">1.0.2</a></li>
openssl-commits mailing list
To unsubscribe:

Reply via email to