$ tag log -- master+
$ tig log -- master
X-Git-Url: https://git.distorted.org.uk/~mdw/tig/blobdiff_plain/53b90d52aa36051fcbb16775016c8649828b97ea..562355762b4c6fd37e5a8c2383278587efa447d6:/tig.1.html?ds=sidebyside 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 -
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.
-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.
+If you are interested only in those revisions that made changes to a specific file (or even several files) list the files like this:
$ tag log -- master+
$ tig log -- master
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". |
Alternatively, commits can be limited to a specific range, such as "all commits between tag-1.0 and tag-2.0". For example:
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:
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.
+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/+
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+