From 9b72a2e674f7cbc320b0b72fc71ad813d296ab12 Mon Sep 17 00:00:00 2001
From: James Moger <james.moger@gitblit.com>
Date: Thu, 22 Sep 2011 12:04:43 -0400
Subject: [PATCH] Updated to JGit 1.1.0 and reverse-sort library dependencies.

---
 docs/01_setup.mkd |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/01_setup.mkd b/docs/01_setup.mkd
index 37605c9..1c8db12 100644
--- a/docs/01_setup.mkd
+++ b/docs/01_setup.mkd
@@ -32,7 +32,7 @@
 ### Creating your own Self-Signed Certificate
 Gitblit GO automatically generates an ssl certificate for you that is bound to *localhost*.
 
-Remote Eclipse/EGit/JGit clients (<= 1.0.0) will fail to communicate using this certificate because JGit always verifies the hostname of the certificate, regardless of the *http.sslVerify=false* client-side setting.
+Remote Eclipse/EGit/JGit clients (<= 1.1.0) will fail to communicate using this certificate because JGit always verifies the hostname of the certificate, regardless of the *http.sslVerify=false* client-side setting.
 
 The EGit failure message is something like:
 
@@ -307,7 +307,7 @@
 **NOTE:**<br/>
 The default self-signed certificate generated by Gitlbit GO is bound to *localhost*.<br/>
 If you are using Eclipse/EGit/JGit clients, you will have to generate your own certificate that specifies the exact hostname used in your clone/push url.<br/>
-You must do this because Eclipse/EGit/JGit (<= 1.0.0) always verifies certificate hostnames, regardless of the *http.sslVerify=false* client-side setting. 
+You must do this because Eclipse/EGit/JGit (<= 1.1.0) always verifies certificate hostnames, regardless of the *http.sslVerify=false* client-side setting. 
  
 - Eclipse/EGit/JGit
     1. Window->Preferences->Team->Git->Configuration

--
Gitblit v1.9.1