openldap.git branch mdb.master updated. e46d78b7b083c3a9983f8a0e77b90bccd64b6ec9
by openldap-commit2devel@OpenLDAP.org
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 e59fb2eccbdacc43a04f2c100186a4dad4e593cc (commit)
discards f6e98cd66f671030cf4344854a316b438ee8f967 (commit)
discards 9459346e7bacecfd513ac76503c699c11e82f7a0 (commit)
discards 7e8d9290f0f8eaea126b5f85a924f5a817ce2179 (commit)
via e46d78b7b083c3a9983f8a0e77b90bccd64b6ec9 (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 (e59fb2eccbdacc43a04f2c100186a4dad4e593cc)
\
N -- N -- N (e46d78b7b083c3a9983f8a0e77b90bccd64b6ec9)
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 e46d78b7b083c3a9983f8a0e77b90bccd64b6ec9
Author: Howard Chu <hyc(a)symas.com>
Date: Wed Feb 17 17:27:50 2016 +0000
MDB_VL32 - increase max write txn size
-----------------------------------------------------------------------
Summary of changes:
libraries/liblmdb/mdb.c | 25 +------------------------
1 file changed, 1 insertion(+), 24 deletions(-)
---
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git