From d62d883423c4f13e9514c203d2f0b14e4715df7f Mon Sep 17 00:00:00 2001
From: James Moger <james.moger@gitblit.com>
Date: Fri, 23 May 2014 09:19:01 -0400
Subject: [PATCH] Tag server-side merges when incremental push tags are enabled

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

diff --git a/src/site/tickets_setup.mkd b/src/site/tickets_setup.mkd
index c098f4c..aeecbeb 100644
--- a/src/site/tickets_setup.mkd
+++ b/src/site/tickets_setup.mkd
@@ -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