README.markdown in svn2git-1.3.1 vs README.markdown in svn2git-1.3.2

@@ -62,14 +62,16 @@
 the svn repo.
 
 Installation
 ------------
 
-Make sure you have git installed, then install the gem:
+Make sure you have git, ruby and rubygems installed, then install the gem:
 
-    $ sudo apt-get install git-core git-svn
-    $ sudo gem install nirvdrum-svn2git
+    $ sudo apt-get install git-core git-svn ruby rubygems
+    $ sudo gem install svn2git --source http://gemcutter.org
+    
+*NB: Previous versions of the gem could be installed from GitHub as nirvdrum-svn2git.  You can install that gem via `$ sudo gem install nirvdrum-svn2git --source http://gems.github.com`, but the nirvdrum-svn2git gem will no longer be updated.  Please use the one hosted on gemcutter.*
 
 Usage
 -----
 
 There are a number of ways in which you can create a git repo from an existing
@@ -128,10 +130,21 @@
 Alternatively, you can place the authors file into ~/.svn2git/authors and
 svn2git will load it out of there. This allows you to build up one authors
 file for all your projects and have it loaded for each repository that you
 migrate.
 
+If you need a jump start on figuring out what users made changes in your
+svn repositories the following command sequence might help. It grabs all
+the logs from the svn repository, pulls out all the names from the commits,
+sorts them, and then reduces the list to only unique names. So, in the end
+it outputs a list of usernames of the people that made commits to the svn
+repository which name on its own line. This would allow you to easily
+redirect the output of this command sequence to ~/.svn2git/authors and have
+a very good starting point for your mapping.
+
+    $ svn log | grep -E "r[0-9]+ \| [a-z]+ \|" | awk '{print $3}' | sort | uniq
+
 Debugging
 ---------
 
 If you're having problems with converting your repository and you're not sure why,
 try turning on verbose logging.  This will print out more information from the
@@ -167,6 +180,6 @@
     If we were to reference the parent of this svn tagged commit there could
     potentially be situations where a developer would checkout a tag in git
     and the resulting code base would be different then if they checked out
     that very same tag in the original svn repo. This is only due to the fact
     that the svn tags allow changesets in them, making them not just annotated
-    tags.
\ No newline at end of file
+    tags.