Changes between Version 19 and Version 20 of TracTicketChangelogPlugin

Timestamp:

Mar 13, 2015, 12:20:01 PM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes, tagged with license

TracTicketChangelogPlugin

@@ -19 +19 @@
 
 === Mercurial
-For mercurial backend, since [http://trac.edgewall.org/ticket/8417 TracMecurial did not support repository cache] yet, you should install [http://github.com/maraujop/TracMercurialChangesetPlugin TracMercurialChangesetPlugin] to generate repository cache.
+
+For mercurial backend, since [http://trac.edgewall.org/ticket/8417 TracMecurial did not support repository cache] yet, you should install [http://github.com/maraujop/TracMercurialChangesetPlugin TracMercurialChangesetPlugin] to generate the repository cache.
 
 === Git
-For git backend, according to #7746, you should add following config to git section:
+
+For git backend, according to #7746, you should add following config to git section in the `trac.ini` file:
 {{{#!ini
 [git]
@@ -28 +30 @@
 persistent_cache = true
 }}}
+
 You might need to run `trac-admin repository resync` after the change.
 
@@ -56 +59 @@
 You can check out TracTicketChangelogPlugin from [http://trac-hacks.org/svn/tracticketchangelogplugin here] using Subversion, or [source:tracticketchangelogplugin browse the source] with Trac.
 
-== Install
+== Installation
+
 You can install this plugin following the standard procedures described in [wiki:TracPlugins#InstallingaTracplugin].
 
@@ -62 +66 @@
  1. Change to the directory containning setup.py.
   * (Optional): If you are using Trac 0.12 with i18n, you should compile language files here:
- {{{#!sh
+{{{#!sh
 python setup.py compile_catalog -f
 }}} 
@@ -73 +77 @@
 cp dist/*.egg /srv/trac/env/plugins
 }}}
- 1. Config trac.ini:
- {{{#!ini
+ 1. Add the following to the `trac.ini` file in the components section:
+{{{#!ini
 [components]
 ticketlog.* = enabled
@@ -86 +90 @@
 
 === Usage
- * make sure you add `TICKETLOG_VIEW` permission to users
- * you can config log_pattern to define your pattern.[[br]]
+
+ * Make sure you add `TICKETLOG_VIEW` permission to users.
+ * You can configure the log_pattern to define your pattern:[[br]]
    `%s` in the pattern will be replaced with the referenced ticket number (e.g. 12345), so `\s*#%s+\s+.*` will be evaluated as `\s*#12345+\s+.*`.