After using GoogleCode to Git Exporter, using SVN via Git yields wrong/randomized revision numbers

[GoogleCodeExporter]

Exporter completes successfully and GitHub web page can be accessed fine.  
However, if I use SVN to pull down a snapshot via GitHub's SVN support, the 
revision numbers indicated in verbose logging are wrong.  I'm aware GitHub 
itself doesn't use revision numbers, but the SVN client feature supports them - 
however the exporter is not creating them properly to match the original 
GoogleCode Project.

In my case, the project is for historical reference only - it won't be 
committed to any more, but we want the GoogleCode/original revision numbers 
present so that you can find references to such revisions in the comments.

Is there any way to run the exporter and preserve the original numbers?

Original issue reported on code.google.com by bobbitdi...@gmail.com on 12 Jun 2015 at 11:37

[GoogleCodeExporter]

Unfortunately no. The Google Code to GitHub exporter essentially calls into the 
API that underpins import.github.com. There aren't many configuration options 
here, so if GitHub's SVN support doesn't provide revision number mappings there 
isn't anything we can do on our end.

Original comment by chrsm...@google.com on 16 Jun 2015 at 8:11

• Changed state: Infeasible
• Added labels: Component-ExporterTool

[GoogleCodeExporter]

So if GitHub somehow allowed a map to be applied to its SVN APIs, who would 
create that map?  Are you proposing that each GoogleCode exporter customer has 
to manually write some tool to scan both SVN trees and generate such a map?

Or if I can get GitHub interested, are you saying the owners of the export tool 
would provide such a map generator? (Seems like it would be a joint project, 
right?)

Original comment by bobbitdi...@gmail.com on 17 Jun 2015 at 4:43