A ref change was pushed to the OpenLDAP (openldap.git) repository.
It will be available in the public mirror shortly.
The branch, mdb.master has been updated
discards 2e386ec81f537e32a1734ef8737a09aa66d1028a (commit)
via 4d2154397afd90ca519bfa102b2aad515159bd50 (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 (2e386ec81f537e32a1734ef8737a09aa66d1028a)
\
N -- N -- N (4d2154397afd90ca519bfa102b2aad515159bd50)
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.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 4d2154397afd90ca519bfa102b2aad515159bd50
Author: Howard Chu <h...@openldap.org>
Date: Thu Mar 23 20:37:24 2017 +0000
ITS#8622 fix xcursor after cursor_del
Re-fix 6b1df0e4c7fadd21d1233d7157229b2d89ccaa04 from ITS#8406
-----------------------------------------------------------------------
Summary of changes:
libraries/liblmdb/mdb.c | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
---
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git
