This is an automated email from the ASF dual-hosted git repository.
rnewson pushed a change to branch lucene-10
in repository https://gitbox.apache.org/repos/asf/couchdb.git
discard afdf025f8 Move up to match Lucene source compatibility
discard 16474e446 document nouveau handling of lucene 9 & 10
discard 63a5ca74e fix formatting error in previous PR
discard 3d92f2292 add scanner to upgrade nouveau indexes
discard b551a2f54 insert lucene version in new design documents if missing
discard 64d6beec0 nouveau welcome message for version negotiation
discard ba8daae9d support legacy codec but prevent new legacy indexes
add 33f4c4e1b support legacy codec but prevent new legacy indexes
add 535079cf9 nouveau welcome message for version negotiation
add 88a5983ff insert lucene version in new design documents if missing
add 1943b1444 add scanner to upgrade nouveau indexes
add 191763f9e fix formatting error in previous PR
add 2a7aff155 document nouveau handling of lucene 9 & 10
add e8b217696 Move up to match Lucene source compatibility
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (afdf025f8)
\
N -- N -- N refs/heads/lucene-10 (e8b217696)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../src/main/java/org/apache/couchdb/nouveau/core/IndexManager.java | 4 ----
1 file changed, 4 deletions(-)
