summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorAlbert Zeyer <albert.zeyer@rwth-aachen.de>2011-05-13 14:49:03 +0200
committerAlbert Zeyer <albert.zeyer@rwth-aachen.de>2011-05-13 14:49:03 +0200
commit4aff509e6cba68a756e23c3cddb3491472a30e51 (patch)
tree071721c95d9dbb7c462eb71f360200514bdf8ccf /README.md
parentad7f699e39fb8474eb6405e821e0ec2bedeab12f (diff)
no point in keeping two readmes
Diffstat (limited to 'README.md')
-rw-r--r--README.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/README.md b/README.md
index 28998a6..4211bca 100644
--- a/README.md
+++ b/README.md
@@ -22,6 +22,12 @@ Limitations:
* Only a single tracker is supported, though this could be easily fixed.
* All issues and comments will be owned by the project's owner on GitHub, but mention the SF username of the original submitter.
* There's some rubbish in the comment text sometimes (Logged In, user_id, Originator) but this is in the SF XML export.
+* There are encoding errors in the SF export of (at least) comments. Non-ASCII characters are encoded with UTF-8, then decoded (interpreted) as CP1252, and those code points gets encoded as XML entities. The script does not work around this. See also http://stackoverflow.com/questions/5291081/how-did-sourceforge-maim-this-unicode-character
+
+Code migration
+--------------
+
+This script doesn't help you to migrate code from SF's Subversion to GitHub. However, I found the following page helpful in doing that: http://help.github.com/svn-importing/
Usage
-----