On 11/9/2017 3:56 AM, TOM wrote: > Thanks for your patience and helps. > > Recently, I acquired a batch of commits’ SHA data of Lucene, of which > the time span is from 2010 to 2015. In order to get original info, I tried to > use these SHA data to track commits. First, I cloned Lucene repository to my > local host, using the cmd git clone https:// > https://github.com/apache/lucene-solr.git. Then, I used git show [commit SHA] > to get commits’ history record, but failed with the CMD info like this: > >>> git show be5672c0c242d658b7ce36f291b74c344de925c7
Where did this information originate? 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. https://issues.apache.org/jira/browse/LUCENE-6937 It is very likely that every SHA hash in github changed when that happened. If the information you are referencing was built from github *before* the official repository was changed, it is likely that it is completely useless now. The fact that your information covers 2010 to 2015 probably means that it was generated from that repository that no longer exists. Thanks, Shawn
