README.markdown in gitolite-1.0.1 vs README.markdown in gitolite-1.1.0

@@ -7,13 +7,10 @@
 ## Features ##
 * Allows for the creation and management of repos within gitolite
 * Allows for the creation and deletion of SSH keys within gitolite
 * Allows for the bootstrapping of a gitolite-admin repository
 
-## Issues ##
-* Gem is not thread safe.  For now, the gem will change directories in order to perform git operations.  It will, however, return to the old working directory once it is finished.  I am looking into making the gem thread safe.
-
 ## Requirements ##
 * Ruby 1.8.x or 1.9.x
 * a working [gitolite](https://github.com/sitaramc/gitolite) installation
 * the <tt>gitolite-admin</tt> repository checked out locally
 
@@ -158,9 +155,12 @@
 
 The gitolite gem, on the other hand, will <em>always</em> output groups so that all modifications are represented before it is ever used.  For the above example, group b will be output with the following users: <tt>jim, bob, joe, sue, and sam</tt>.  The groups in the config file will look like this:
 
     @groupa = bob joe sue sam
     @groupb = jim @groupa
+
+## Issues ##
+* Gem is not thread safe.  For now, the gem will change directories in order to perform git operations.  It will, however, return to the old working directory once it is finished.  I am looking into making the gem thread safe.  Note that this is only an issue on Rubies that do not have a GIL (ex jRuby or Rubinius)
 
 # Contributing #
 * Tests!  If you ask me to pull changes that are not adequately tested,  I'm not going to do it.
 * If you introduce new features/public methods on objects, you must update the README.