summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 0721c53)
raw | patch | inline | side by side (parent: 0721c53)
author | Jonas Fonseca <fonseca@diku.dk> | |
Tue, 16 May 2006 13:44:25 +0000 (15:44 +0200) | ||
committer | Jonas Fonseca <fonseca@antimatter.localdomain> | |
Tue, 16 May 2006 13:44:25 +0000 (15:44 +0200) |
tig.c | patch | blob | history |
index b6c46ad31879cfa59cafdac3ffe57bfbaf1ef7bb..51cb6063d5d062b879bb1bfe8c537896b5dffb3f 100644 (file)
--- a/tig.c
+++ b/tig.c
* or otherwise limit the view to. Note, that tig(1) does not itself parse
* the described revision options.
*
+ * File history
+ * ------------
+ * If you are interested only in those revisions that made changes to a
+ * specific file (or even several files) list the files like this:
+ *
+ * $ tig log Makefile
+ *
+ * To avoid ambiguity with repository references such as tag name, be sure
+ * to separate file names from other git options using "\--". So if you
+ * have a file named 'master' it will clash with the reference named
+ * 'master', and thus you will have to use:
+ *
+ * $ tag log -- master
+ *
+ * NOTE: For the main view, avoiding ambiguity will in some cases require
+ * you to specify two "\--" options. The first will make tig(1) stop
+ * option processing and the latter will be passed to git log.
+ *
* Limit by date or number
* ~~~~~~~~~~~~~~~~~~~~~~~
* To speed up interaction with git, you can limit the amount of commits