Github user NightOwl888 commented on the issue:
https://github.com/apache/lucenenet/pull/179
Okay, this is ready for review/merge now. I have synced it up with the
master branch already, so there are some commits you have already reviewed
here. But you can merge the master branch
Github user ChristopherHaws commented on the issue:
https://github.com/apache/lucenenet/pull/181
Sounds good. I will take a look at the collation namespace tonight when I
get home from work.
Thanks!
---
If your project is set up for it, you can reply to this email and have
Github user NightOwl888 commented on the issue:
https://github.com/apache/lucenenet/pull/181
Sure. I am currently working on
https://github.com/NightOwl888/lucenenet/commits/analysis-work-2, which I plan
to merge into #179 (probably within the next few hours).
About the only
Github user NightOwl888 commented on the issue:
https://github.com/apache/lucenenet/pull/179
I am working on wrapping this up now. Lucene.Net.Analysis.Common is now
ported completely except for the Collation namespace and a few odd tests.
I have morphed the Lucene 6.1.0
Github user NightOwl888 commented on the issue:
https://github.com/apache/lucenenet/pull/181
Actually, all of this is already done in #179.
I am intrigued about the EntryIterator bug fix, though. The solution I came
up with was to maintain an internal dictionary and return
Github user synhershko commented on the issue:
https://github.com/apache/lucenenet/pull/181
Awesome, thanks! Can you please check
https://github.com/apache/lucenenet/pull/179 to see you and @NightOwl888 aren't
working on the same stuff?
---
If your project is set up for it, you can
