Oh I *have* downloaded the CVS source and I actually did *fix* (maybe) two of these three bugs and I did *submit* what I did exactly to fix them to the sourceforge &/ mailing-list for public review (but not in diff/patch format since they were one-liners). The problem is that much of Lucene is very complicated (understandably so) and I never got someone more familiar with Lucene's more complicated parts (like Doug, or perhaps some others here) to respond to see if my fix was correct and completely addresses the issue. Not one person responded except for some other guy to say he experienced the same bug and that nobody responded to his bug report either :-(. The 3rd bug, the one that I didn't fix, I took the time to write a test program that showed the bug. What's needed now for these bugs to be squashed, is someone that really knows Lucene's complicated parts to verify if my 2 fixes are sufficient and to at least investigate the 3rd bug. I'm not the one with years of search-engine writing experience ;-).
I really appreciate your response by the way, it's a welcome change... and an initial step. ~ Dave Smiley On Saturday, March 16, 2002, at 08:59 PM, Andrew C. Oliver wrote: > You need not be asked, help is always wanted. How about instead of > submitting bugs, submit patches. Simply get the sources via CVS (click > on CVS Repository on the Jakarta front page), fix the bugs and then do > cvs diff -u to create patches. Post those into bugzilla and put > [PATCH] > on the summary line and I think you'll find them applied rather > quickly. > > -Andy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
