From 3b23dcdde4ef55927e45e56596e7023ce2cf9424 Mon Sep 17 00:00:00 2001
From: James Moger <james.moger@gitblit.com>
Date: Wed, 07 May 2014 14:32:09 -0400
Subject: [PATCH] Consolidate open tickets page parameters

---
 src/site/tickets_setup.mkd |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/site/tickets_setup.mkd b/src/site/tickets_setup.mkd
index ee27b44..aeecbeb 100644
--- a/src/site/tickets_setup.mkd
+++ b/src/site/tickets_setup.mkd
@@ -20,7 +20,7 @@
 
     tickets.service = com.gitblit.tickets.BranchTicketService
 
-Your ticket journals are persisted to `id/{shard}/{id}/journal.json`.  These journals are stored on an orphan branch, `refs/gitblit/tickets`, within your repository.  This allows you to easily clone your entire ticket history to client working copies or to mirrors.
+Your ticket journals are persisted to `id/{shard}/{id}/journal.json`.  These journals are stored on an orphan branch, `refs/meta/gitblit/tickets`, within your repository.  This allows you to easily clone your entire ticket history to client working copies or to mirrors.
 
 #### Redis Ticket Service
 
@@ -28,7 +28,7 @@
 
 Your ticket journals are persisted to a Redis data store.  *Make sure you configure your Redis instance for durability!!*  This particular service is highly-scalable and very fast.  Plus you can use all of the power of Redis replication, should you want.
 
-The main drawback to this service is that Redis is primarily a Unix tool and works best on a Unix server.  While there is a Windows port, sort-of maintained by Microsoft, it is not actively updated.
+The main drawback to this service is that Redis is primarily a Unix tool and works best on a Unix server.  Microsoft is engaged with the Redis community and they do maintain a semi-active port of Redis for Windows servers.
 
     tickets.redis.url = redis://(:{password}@){hostname}:{port}(/{databaseId})
 

--
Gitblit v1.9.1