rlw730 / support-tools

Automatically exported from code.google.com/p/support-tools
Apache License 2.0
0 stars 0 forks source link

SVN username mapping #25

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
There seems to be no possibility to map the SVN user names in commits? I added 
my gmail-Adress to the Github settings, but on every commit, it still shows: 
"Invalid author email".

Docs on 
https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/ 
say: This means the email address in your local Git configuration settings is 
either blank or not formatted as an email address. You will need to change the 
email address in your local Git configuration settings, then add the new 
address to your GitHub email settings to link your future commits. Old commits 
will not be linked.

This is not good, because by that I loose my committer credits on OpenHUB / and 
others.

Original issue reported on code.google.com by uwe.h.schindler on 13 Mar 2015 at 11:11

GoogleCodeExporter commented 8 years ago
The project is still migrating, but the code is already transferred: 
https://github.com/uschindler/forbidden-apis

Original comment by uwe.h.schindler on 13 Mar 2015 at 11:12

GoogleCodeExporter commented 8 years ago
I fixed the usernames manually by cloning the repo with "--mirror" and 
rewriting history and pushing back again.

The other related thing thats not good with the exporter: On exported issues, 
it preserves the user name / e-mail address in an incomplete form. So when 
resolving open issues you have no chance to inform the original reporter, 
because you cannot see e-mail address.

Original comment by uwe.h.schindler on 14 Mar 2015 at 11:34

GoogleCodeExporter commented 8 years ago
We've added a new section to the Google Code Exporter to cover this issue. (How 
to fix up the source from GitHub, after the export is complete.)

https://code.google.com/p/support-tools/wiki/GitHubExporterFAQ#Fixing_author_inf
ormation_(SVN_only)

Original comment by chrsm...@google.com on 16 Mar 2015 at 1:49