And here is IndexWriter with initial revision in 2001, but again git
still only stops at Feb 7, 2012.
http://svn.apache.org/viewvc/lucene/dev/trunk/lucene/core/src/java/org/apache/lucene/index/IndexWriter.java?view=log

Revision 149570 - (view) (download) (annotate) - [select for diffs]
Added Tue Sep 18 16:29:48 2001 UTC (13 years, 8 months ago) by jvanzyl
Original Path: 
lucene/java/trunk/src/java/org/apache/lucene/index/IndexWriter.java
File length: 15076 byte(s)

Initial revision

So subversion history looks pretty complete. If we can add other
history from sourceforge, fantastic, but there isn't so so much going
on there.

It is git that is totally broken here with respect to history.


On Sun, May 31, 2015 at 6:47 PM, Robert Muir <[email protected]> wrote:
> On Sun, May 31, 2015 at 4:39 PM, [email protected]
> <[email protected]> wrote:
>>
>> If we were to come up with a new git repo that doesn’t have the ‘.jar’s,
>> it’d be good to also streamline the history prior to the big Lucene + Solr
>> merge due to the paths in source control as to where the trunk, branches,
>> and tags lived.  It appears the current repo may have been a blind git
>> import from subversion.  And hand-done process that is mindful of these
>> things would result in a nice history.  I’ve done this sorta thing once (a
>> project at my last job) and volunteer to do it here if we can get consensus
>> on a move to git.
>
> The current Git history is totally broken. This is a complete
> dealbreaker from my perspective, if its indicative of what svn -> git
> conversion will produce.
>
> Look at CheckIndex.java history in git:
>
> https://github.com/apache/lucene-solr/commits/trunk/lucene/core/src/java/org/apache/lucene/index/CheckIndex.java?page=5
> It stops at Feb 7, 2012.
>
> In subversion it goes back to 2007, to the original issue where Mike
> added CheckIndex:
> http://svn.apache.org/viewvc/lucene/dev/trunk/lucene/core/src/java/org/apache/lucene/index/CheckIndex.java?view=log

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to