X-Git-Url: https://git.distorted.org.uk/~mdw/tig/blobdiff_plain/53b90d52aa36051fcbb16775016c8649828b97ea..562355762b4c6fd37e5a8c2383278587efa447d6:/tig.1.html diff --git a/tig.1.html b/tig.1.html index 9d3f59c..6a834f1 100644 --- a/tig.1.html +++ b/tig.1.html @@ -776,14 +776,17 @@ n -

Specifying revisions

+

Revision specification

This section describes various ways to specify what revisions to display -or otherwise limit the view to. Note, that tig(1) does not itself parse -the described revision options.

-
-

File history

-
+or otherwise limit the view to. tig(1) does not itself parse the described +revision options so refer to the relevant git man pages for futher +information. Relevant man pages besides git-log(1) are git-diff(1) and +git-rev-list(1).

+

You can tune the interaction with git by making use of the options +explained in this section. For example, by configuring the environment +variables described in the "View commands" section.

+

Limit by path name

If you are interested only in those revisions that made changes to a specific file (or even several files) list the files like this:

@@ -796,7 +799,7 @@ have a file named master it will clash with the reference named master, and thus you will have to use:

-
$ tag log -- master
+
$ tig log -- master
@@ -812,17 +815,23 @@ option processing and the latter will be passed to git log.

To speed up interaction with git, you can limit the amount of commits to show both for the log and main view. Either limit by date using e.g. --since=1.month or limit by the number of commits using -n400.

+

If you are only interested in changed that happened between two dates +you can use:

+
+
+
$ tig -- --after=May.5th --before=2006-05-16.15:44
+
- +
Note
You can tune the interaction with git by making use of the options -explained in this section. For example, by configuring the environment -variables described in the "View commands" section.The dot (".") is used as a separator instead of a space to avoid +having to quote the option value. If you prefer use --after="May 5th" +instead of --after="May 5th".
-

Ranges

+

Limiting by commit ranges

Alternatively, commits can be limited to a specific range, such as "all commits between tag-1.0 and tag-2.0". For example:

@@ -841,7 +850,9 @@ upstream remote branch, using:

Limiting by reachability

Git interprets the range specifier "tag-1.0..tag-2.0" as "all commits reachable from tag-2.0 but not from tag-1.0". -If you prefer to specify which commit to preview in this way use the +Where reachability refers to what commits are ancestors (or part of the +history) of the branch or tagged revision in question.

+

If you prefer to specify which commit to preview in this way use the following:

@@ -850,6 +861,23 @@ following:

You can think of ^ as a negation operator. Using this alternate syntax, it is possible to further prune commits by specifying multiple branch cut offs.

+

Combining revisions specification

+

Revisions options can to some degree be combined, which makes it possible +to say "show at most 20 commits from within the last month that changed +files under the Documentation/ directory."

+
+
+
$ tig -- --since=1.month -n20 -- Documentation/
+
+

Examining all repository references

+

In some cases, it can be useful to query changes across all references +in a repository. An example is to ask "did any line of development in +this repository change a particular file within the last week". This +can be accomplished using:

+
+
+
$ tig -- --all --since=1.week -- Makefile
+

BUGS

@@ -898,7 +926,7 @@ gitview(1): git repository browser written using python/gtk.