The branch master has been updated
discards 578ef142566c4cff4c0276cb3d38f571a991f8e7 (commit)
via 39375a75ebb1997d79bff3712957fe8362acbbd2 (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 (578ef142566c4cff4c0276cb3d38f571a991f8e7)
\
N -- N -- N (39375a75ebb1997d79bff3712957fe8362acbbd2)
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 39375a75ebb1997d79bff3712957fe8362acbbd2
Author: Richard Levitte <[email protected]>
Date: Tue Feb 13 15:17:00 2018 +0100
Add 1.1.1 stuff
-----------------------------------------------------------------------
Summary of changes:
_____
openssl-commits mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-commits
