{section: Installing a commit message template}
+You may find it helpful to install a git commit message template, so that some basic gliss glosses are right in front of you as you're editing the commit message. You can do this with git options. First, copy the following text to a file in your home directory (call it something like =.glisscommittemplate=):
+
+ # To use any of these glosses in your commit message, uncomment
+ # the initial # and edit the gloss text as appropriate.
+ #
+ #===GT=== #1234
+ #===GT:Fixed=== #1234
+ #===VersionHistory===
+ #===UpgradeNote===
+
+Then, tell =git= where to find this template:
+
+ git config --global commit.template ~/.glisscommittemplate
+
+(Use =--global= or not depending on whether you'd rather opt-out of this template for individual repositories or opt-in per repository.)
+
{section: Installing gliss}
-The easiest way to install gliss is to use the {link: http://rubygems.org/gems/gliss RubyGem} package.
+The easiest way to install gliss is to use the {link: http://rubygems.org/gems/gliss RubyGem} package. You may need to use the =--user-install= option to =gem install= or run as root.
{section: Inspecting glosses}
+
+The basic way to use =gliss= is to give it two branch names, like =gliss V7_5_4 V7_5_5=. It will find all of the glosses in commit messages associated with commits that are reachable from =V7_5_5= but not =V7_5_4=. There are other options, too; run =gliss --help= for more information.
