The branch master has been updated
discards 39375a75ebb1997d79bff3712957fe8362acbbd2 (commit)
via ae0b9d5e0f284758eb8b5998a530ee25c52a6bb4 (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 (39375a75ebb1997d79bff3712957fe8362acbbd2)
\
N -- N -- N (ae0b9d5e0f284758eb8b5998a530ee25c52a6bb4)
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 ae0b9d5e0f284758eb8b5998a530ee25c52a6bb4
Author: Richard Levitte <levi...@openssl.org>
Date: Tue Feb 13 15:17:00 2018 +0100
Add 1.1.1 stuff
-----------------------------------------------------------------------
Summary of changes:
Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile b/Makefile
index d3295b8..37b91be 100644
--- a/Makefile
+++ b/Makefile
@@ -17,6 +17,7 @@ SIMPLE = newsflash.inc sitemap.txt \
news/cl102.txt news/cl110.txt \
news/openssl-1.0.2-notes.inc \
news/openssl-1.1.0-notes.inc \
+ news/openssl-1.1.1-notes.inc \
news/newsflash.inc \
news/vulnerabilities.inc \
news/vulnerabilities-1.1.1.inc \
_____
openssl-commits mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-commits
