lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Currens <currens.ch...@gmail.com>
Subject Re: [Lucene.Net] Merge 3.0.3 into trunk and other forward progress
Date Fri, 30 Dec 2011 03:35:28 GMT
Some fixes might already be in trunk, the 2.9.4g branch and even the 3.0.3
branch.  I can tell you that the code that the 3.0.3 branch was ported from
was the downloadable source, sometime around september/october and not
directly from SVN.  Assuming that Lucene's Jira is correct, then all issues
that have a fix version of 3.0.3, should already be ported in the 3.0.3
branch.  Of course, I'm not sure if Java lucene does revision versions to
fix other bugs (like if they have a 3.0.3.x version), so
I'm unfortunately in that same boat as you when it comes to knowing the
EXACT state of at least the 3.0.3 branch.  I've been meaning do diff the
source I've downloaded against whatever tag I can find, and hopefully get
some bearings on exactly what changeset that branch is at right now.

Thanks,
Christopher

On Thu, Dec 29, 2011 at 12:06 PM, Rory Plaire <codekaizen@gmail.com> wrote:

> Might some of these fixes already be in the Lucene.Net codebase? For
> example, when I looked at the subversion commits for
> https://issues.apache.org/jira/browse/LUCENE-2620 I found that the changes
> appear already in both the trunk and in the 2.9.4g branch. I'm not sure of
> the provenance of the current Lucene.Net codebase, and therefore how to
> interpret this finding.
> -r
> On Wed, Dec 28, 2011 at 10:46 PM, Prescott Nasser <geobmx540@hotmail.com
> >wrote:
>
> > Yeah that would work
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message