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 91eacb469 Move up to match Lucene source compatibility
discard 84b8345fd document nouveau handling of lucene 9 & 10
discard ea10d6be9 fix formatting error in previous PR
discard abd93d697 add scanner to upgrade nouveau indexes
discard 01b3706d9 insert lucene version in new design documents if missing
discard 4dc1ea215 Allow existing legacy indexes but prevent new ones
add 7aa7dc200 Allow existing legacy indexes but prevent new ones
add 3d59f9896 insert lucene version in new design documents if missing
add 73285a67f add scanner to upgrade nouveau indexes
add a337bb123 fix formatting error in previous PR
add 1d6c49662 document nouveau handling of lucene 9 & 10
add de2520703 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 (91eacb469)
\
N -- N -- N refs/heads/lucene-10 (de2520703)
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/nouveau/src/nouveau_api.erl | 2 --
1 file changed, 2 deletions(-)
