StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In order to fix the "invalid-email-address" issue you have to find old "git author names" in commits and set new names and email addresses of the "Author" and "Committer" for the commits <em>before</em> you push newly converted repository to GutHub.</p> <p>This fix (search and replace...) is done using "git filter-branch" command. You may see ready to use example here: (now it's dead?!) <a href="http://www.theleagueofpaul.com/hg-to-git.html" rel="nofollow">Mercurial to Git, solving "invalid-email-address"</a> </p> <p>[Edited:] As the link above is dead now, I provide my example of the "fix-user-email.sh" file below. As yo may see, here two variants of an author name are being translated into the same valid GIT name/email pair:</p> <pre><code>git filter-branch --env-filter ' an="$GIT_AUTHOR_NAME" am="$GIT_AUTHOR_EMAIL" cn="$GIT_COMMITTER_NAME" cm="$GIT_COMMITTER_EMAIL" if [ "$GIT_AUTHOR_NAME" = "peter.pen" ] then cn="peterpen" cm="peterpen@example.com" an="peterpen" am="peterpen@example.com" fi if [ "$GIT_AUTHOR_NAME" = "peterpen" ] then cn="peterpen" cm="peterpen@example.com" an="peterpen" am="peterpen@example.com" fi export GIT_AUTHOR_NAME="$an" export GIT_AUTHOR_EMAIL="$am" export GIT_COMMITTER_NAME="$cn" export GIT_COMMITTER_EMAIL="$cm" ' </code></pre> <p>I personally executed commands from the above mentioned page step by step in cygwin bash window (actually I ran/modified/re-ran a script in order to simplify my life, of course :-) ) and checked results using GIT-GUI...</p> <p>When you are ready to test repository on GitHub,</p> <ol> <li>Create new repository at GitHub and do nothing with it!</li> <li>Push converted repo to the Git Hub. If something is not good yet, delete the repo from GitHub and create repo with the same name again...</li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload