README.markdown in svn2git-2.0.0 vs README.markdown in svn2git-2.1.0

@@ -105,10 +105,23 @@
 5. The svn repo is in the standard layout but you want to exclude the massive
 doc directory and the backup files you once accidently added.
 
         $ svn2git http://svn.example.com/path/to/repo --exclude doc --exclude '.*~$'
 
+6. The svn repo actually tracks several projects and you only want to migrate
+one of them.
+
+        $ svn2git http://svn.example.com/path/to/repo/nested_project --no-minimize-url
+
+7. The svn repo is password protected.
+
+        $ svn2git http://svn.example.com/path/to/repo --username <<user_with_perms>>
+
+8. You need to migrate starting at a specific svn revision number.
+
+        $ svn2git http://svn.example.com/path/to/repo --revision <<starting_revision_number>>
+
 The above will create a git repository in the current directory with the git
 version of the svn repository. Hence, you need to make a directory that you
 want your new git repo to exist in, change into it and then run one of the
 above commands. Note that in the above cases the trunk, branches, tags options
 are simply folder names relative to the provided repo path. For example if you
@@ -151,10 +164,10 @@
 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
+    $ svn log | grep -E "r[0-9]+ \| .+ \|" | awk '{print $3}' | sort | uniq
 
 Debugging
 ---------
 
 If you're having problems with converting your repository and you're not sure why,