From b8e1fa94f3f28a94b466c79b1a4b24c6fd755df1 Mon Sep 17 00:00:00 2001
From: James Moger <james.moger@gitblit.com>
Date: Wed, 12 Mar 2014 21:44:36 -0400
Subject: [PATCH] Improve logging of received patchset command
---
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 b1fa775..c098f4c 100644
--- a/src/site/tickets_setup.mkd
+++ b/src/site/tickets_setup.mkd
@@ -1,6 +1,6 @@
## Setting up Tickets
-*PREVIEW 1.4.0*
+*SINCE 1.4.0*
By default, Gitblit is not configured for Tickets. There are several reasons for this, but the most important one is that you must choose the persistence backend that works best for you.
@@ -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
--
Gitblit v1.9.1