<dd>\r
<p>\r
Is the default view, and it shows a one line summary of each commit\r
- in the chosen list of revision. The summary includes commit date,\r
+ in the chosen list of revisions. The summary includes commit date,\r
author, and the first line of the log message. Additionally, any\r
repository references, such as tags, will be shown.\r
</p>\r
</dd>\r
</dl>\r
</div>\r
-<h2><a id="refspec"></a>Specifying revisions</h2>\r
+<h2><a id="refspec"></a>Revision specification</h2>\r
<div class="sectionbody">\r
<p>This section describes various ways to specify what revisions to display\r
-or otherwise limit the view to. Note, that tig(1) does not itself parse\r
-the described revision options.</p>\r
-</div>\r
-<h2>File history</h2>\r
-<div class="sectionbody">\r
+or otherwise limit the view to. tig(1) does not itself parse the described\r
+revision options so refer to the relevant git man pages for futher\r
+information. Relevant man pages besides git-log(1) are git-diff(1) and\r
+git-rev-list(1).</p>\r
+<p>You can tune the interaction with git by making use of the options\r
+explained in this section. For example, by configuring the environment\r
+variables described in the <a href="#view-commands">"View commands"</a> section.</p>\r
+<h3>Limit by path name</h3>\r
<p>If you are interested only in those revisions that made changes to a\r
specific file (or even several files) list the files like this:</p>\r
<div class="literalblock">\r
<em>master</em>, and thus you will have to use:</p>\r
<div class="literalblock">\r
<div class="content">\r
-<pre><tt>$ tag log -- master</tt></pre>\r
+<pre><tt>$ tig log -- master</tt></pre>\r
</div></div>\r
<div class="admonitionblock">\r
<table><tr>\r
<p>To speed up interaction with git, you can limit the amount of commits\r
to show both for the log and main view. Either limit by date using\r
e.g. <tt>--since=1.month</tt> or limit by the number of commits using <tt>-n400</tt>.</p>\r
+<p>If you are only interested in changed that happened between two dates\r
+you can use:</p>\r
+<div class="literalblock">\r
+<div class="content">\r
+<pre><tt>$ tig -- --after=May.5th --before=2006-05-16.15:44</tt></pre>\r
+</div></div>\r
<div class="admonitionblock">\r
<table><tr>\r
<td class="icon">\r
<div class="title">Note</div>\r
</td>\r
-<td class="content">You can tune the interaction with git by making use of the options\r
-explained in this section. For example, by configuring the environment\r
-variables described in the <a href="#view-commands">"View commands"</a> section.</td>\r
+<td class="content">The dot (".") is used as a separator instead of a space to avoid\r
+having to quote the option value. If you prefer use <tt>--after="May 5th"</tt>\r
+instead of <tt>--after="May 5th"</tt>.</td>\r
</tr></table>\r
</div>\r
-<h3>Ranges</h3>\r
+<h3>Limiting by commit ranges</h3>\r
<p>Alternatively, commits can be limited to a specific range, such as\r
"all commits between <em>tag-1.0</em> and <em>tag-2.0</em>". For example:</p>\r
<div class="literalblock">\r
<h3>Limiting by reachability</h3>\r
<p>Git interprets the range specifier "tag-1.0..tag-2.0" as\r
"all commits reachable from <em>tag-2.0</em> but not from <em>tag-1.0</em>".\r
-If you prefer to specify which commit to preview in this way use the\r
+Where reachability refers to what commits are ancestors (or part of the\r
+history) of the branch or tagged revision in question.</p>\r
+<p>If you prefer to specify which commit to preview in this way use the\r
following:</p>\r
<div class="literalblock">\r
<div class="content">\r
<p>You can think of <em>^</em> as a negation operator. Using this alternate syntax,\r
it is possible to further prune commits by specifying multiple branch\r
cut offs.</p>\r
+<h3>Combining revisions specification</h3>\r
+<p>Revisions options can to some degree be combined, which makes it possible\r
+to say "show at most 20 commits from within the last month that changed\r
+files under the Documentation/ directory."</p>\r
+<div class="literalblock">\r
+<div class="content">\r
+<pre><tt>$ tig -- --since=1.month -n20 -- Documentation/</tt></pre>\r
+</div></div>\r
+<h3>Examining all repository references</h3>\r
+<p>In some cases, it can be useful to query changes across all references\r
+in a repository. An example is to ask "did any line of development in\r
+this repository change a particular file within the last week". This\r
+can be accomplished using:</p>\r
+<div class="literalblock">\r
+<div class="content">\r
+<pre><tt>$ tig -- --all --since=1.week -- Makefile</tt></pre>\r
+</div></div>\r
</div>\r
<h2>BUGS</h2>\r
<div class="sectionbody">\r
<div class="content"><a href="http://www.kernel.org/pub/software/scm/git/docs/">git(7)</a>,\r
<a href="http://www.kernel.org/pub/software/scm/cogito/docs/">cogito(7)</a>\r
gitk(1): git repository browser written using tcl/tk,\r
+qgit(1): git repository browser written using c++/Qt,\r
gitview(1): git repository browser written using python/gtk.</div></div>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-May-2006 15:50:55 CEST\r
+Last updated 17-May-2006 18:10:38 CEST\r
</div>\r
</div>\r
</body>\r