Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SearchFuzzy.pm: do not use non-standard XSNIPPETS command #4780

Merged
merged 1 commit into from
Jan 5, 2024

Conversation

rsto
Copy link
Member

@rsto rsto commented Jan 3, 2024

The XSNIPPETS and XCONVMULTISTANDARD commands in Cyrus got deprecated, so don't keep our test using it.

The XSNIPPETS and XCONVMULTISTANDARD commands in Cyrus got
deprecated, so don't keep our test using it.

Signed-off-by: Robert Stepanek <[email protected]>
@rsto rsto requested review from brong, ksmurchison and elliefm January 3, 2024 08:53
Copy link
Contributor

@ksmurchison ksmurchison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rsto rsto merged commit b750123 into master Jan 5, 2024
2 checks passed
@rsto rsto deleted the cassandane_searchfuzzy_no_xsnippets branch January 5, 2024 08:58
@elliefm elliefm added backport-to-3.6 for PRs that are to be backported to 3.6 backport-to-3.4 for PRs that are to be backported to 3.4 backport-to-3.2 for PRs that are to be backported to 3.2 backport-to-3.8 for PRs that are to be backported to 3.8 backport-to-3.10 for PRs that are to be backported to 3.10 labels Mar 25, 2024
@elliefm elliefm removed backport-to-3.6 for PRs that are to be backported to 3.6 backport-to-3.4 for PRs that are to be backported to 3.4 backport-to-3.8 for PRs that are to be backported to 3.8 backport-to-3.10 for PRs that are to be backported to 3.10 labels May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-to-3.2 for PRs that are to be backported to 3.2 include-in-fastmail
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants