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

Hunspell: don't proceed with other suggestions if we found good REP ones #13156

Merged
merged 2 commits into from
Mar 5, 2024

Conversation

donnerpeter
Copy link
Contributor

This makes "rep" and "ph" from TestHunspellRepositoryTestCases pass on latest revisions of the original Hunspell (after hunspell/hunspell@b88f9ea)

This makes "rep" and "ph" from TestHunspellRepositoryTestCases pass on latest revisions of the original Hunspell (after hunspell/hunspell@b88f9ea)
@donnerpeter donnerpeter requested a review from dweiss March 5, 2024 09:56
@donnerpeter donnerpeter merged commit 51122f8 into apache:main Mar 5, 2024
4 checks passed
@donnerpeter donnerpeter deleted the rep branch March 5, 2024 17:14
donnerpeter added a commit that referenced this pull request Mar 7, 2024
…nes (#13156)

* Hunspell: don't proceed with other suggestions if we found good REP ones

This makes "rep" and "ph" from TestHunspellRepositoryTestCases pass on latest revisions of the original Hunspell (after hunspell/hunspell@b88f9ea)

(cherry picked from commit 51122f8)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants