: In the first few weeks of 2016, the Lucene/Solr project migrated from : svn to git. Prior to this, there was a github mirror of the subversion : repository, but when the official repository was converted, that github : mirror was completely deleted, and replaced with an exact mirror of the : official git repository.
the old "mirror" wasn't really a "mirror" so much as it was a "real time svn-to-git conversion" that happened on the fly and generated synthetic git SHAs for every svn commit. : It is very likely that every SHA hash in github changed when that : happened. If the information you are referencing was built from github it is not just likeley, it is something that absolutely happened, and was discussed at at the time: anyone who had a fork of the "github svn-to-git mirror" needed to abandon it and re-clone the "new" migration which had completley differnet SHAs FWIW: the "mdodsworth/lucene-solr" repo you found on github appears to be some random github user who cloned the "old" github mirror circa ~2014 (prior to the converstion) but never "fetched" new commits after that, nor deleted it once the "real" svn-to-git migration for lucene-solr took place. It's possible if you have a lot of old SHAs that you want to correlate to commits, that you could use that repo to try and identify some of the commits -- but as shawn said: knowing where exactly that list or arbitrary SHAs came from is kind of important for identifying exactly what they mean. Also -- What exactly are you trying to do? what is your objective? https://people.apache.org/~hossman/#xyproblem XY Problem Your question appears to be an "XY Problem" ... that is: you are dealing with "X", you are assuming "Y" will help you, and you are asking about "Y" without giving more details about the "X" so that we can understand the full issue. Perhaps the best solution doesn't involve "Y" at all? See Also: http://www.perlmonks.org/index.pl?node_id=542341 -Hoss http://www.lucidworks.com/
