1GITK(1)                           Git Manual                           GITK(1)
2
3
4

NAME

6       gitk - The Git repository browser
7

SYNOPSIS

9       gitk [<options>] [<revision range>] [--] [<path>...]
10
11

DESCRIPTION

13       Displays changes in a repository or a selected set of commits. This
14       includes visualizing the commit graph, showing information related to
15       each commit, and the files in the trees of each revision.
16

OPTIONS

18       To control which revisions to show, gitk supports most options
19       applicable to the git rev-list command. It also supports a few options
20       applicable to the git diff-* commands to control how the changes each
21       commit introduces are shown. Finally, it supports some gitk-specific
22       options.
23
24       gitk generally only understands options with arguments in the sticked
25       form (see gitcli(7)) due to limitations in the command-line parser.
26
27   rev-list options and arguments
28       This manual page describes only the most frequently used options. See
29       git-rev-list(1) for a complete list.
30
31       --all
32           Show all refs (branches, tags, etc.).
33
34       --branches[=<pattern>], --tags[=<pattern>], --remotes[=<pattern>]
35           Pretend as if all the branches (tags, remote branches, resp.) are
36           listed on the command line as <commit>. If <pattern> is given,
37           limit refs to ones matching given shell glob. If pattern lacks ?,
38           *, or [, /* at the end is implied.
39
40       --since=<date>
41           Show commits more recent than a specific date.
42
43       --until=<date>
44           Show commits older than a specific date.
45
46       --date-order
47           Sort commits by date when possible.
48
49       --merge
50           After an attempt to merge stops with conflicts, show the commits on
51           the history between two branches (i.e. the HEAD and the MERGE_HEAD)
52           that modify the conflicted files and do not exist on all the heads
53           being merged.
54
55       --left-right
56           Mark which side of a symmetric difference a commit is reachable
57           from. Commits from the left side are prefixed with a < symbol and
58           those from the right with a > symbol.
59
60       --full-history
61           When filtering history with <path>..., does not prune some history.
62           (See "History simplification" in git-log(1) for a more detailed
63           explanation.)
64
65       --simplify-merges
66           Additional option to --full-history to remove some needless merges
67           from the resulting history, as there are no selected commits
68           contributing to this merge. (See "History simplification" in git-
69           log(1) for a more detailed explanation.)
70
71       --ancestry-path
72           When given a range of commits to display (e.g.  commit1..commit2 or
73           commit2 ^commit1), only display commits that exist directly on the
74           ancestry chain between the commit1 and commit2, i.e. commits that
75           are both descendants of commit1, and ancestors of commit2. (See
76           "History simplification" in git-log(1) for a more detailed
77           explanation.)
78
79       -L<start>,<end>:<file>, -L:<funcname>:<file>
80           Trace the evolution of the line range given by "<start>,<end>" (or
81           the function name regex <funcname>) within the <file>. You may not
82           give any pathspec limiters. This is currently limited to a walk
83           starting from a single revision, i.e., you may only give zero or
84           one positive revision arguments. You can specify this option more
85           than once.
86
87           Note: gitk (unlike git-log(1)) currently only understands this
88           option if you specify it "glued together" with its argument. Do not
89           put a space after -L.
90
91           <start> and <end> can take one of these forms:
92
93           ·   number
94
95               If <start> or <end> is a number, it specifies an absolute line
96               number (lines count from 1).
97
98           ·   /regex/
99
100               This form will use the first line matching the given POSIX
101               regex. If <start> is a regex, it will search from the end of
102               the previous -L range, if any, otherwise from the start of
103               file. If <start> is “^/regex/”, it will search from the start
104               of file. If <end> is a regex, it will search starting at the
105               line given by <start>.
106
107           ·   +offset or -offset
108
109               This is only valid for <end> and will specify a number of lines
110               before or after the line given by <start>.
111
112           If “:<funcname>” is given in place of <start> and <end>, it is a
113           regular expression that denotes the range from the first funcname
114           line that matches <funcname>, up to the next funcname line.
115           “:<funcname>” searches from the end of the previous -L range, if
116           any, otherwise from the start of file. “^:<funcname>” searches from
117           the start of file.
118
119       <revision range>
120           Limit the revisions to show. This can be either a single revision
121           meaning show from the given revision and back, or it can be a range
122           in the form "<from>..<to>" to show all revisions between <from> and
123           back to <to>. Note, more advanced revision selection can be
124           applied. For a more complete list of ways to spell object names,
125           see gitrevisions(7).
126
127       <path>...
128           Limit commits to the ones touching files in the given paths. Note,
129           to avoid ambiguity with respect to revision names use "--" to
130           separate the paths from any preceding options.
131
132   gitk-specific options
133       --argscmd=<command>
134           Command to be run each time gitk has to determine the revision
135           range to show. The command is expected to print on its standard
136           output a list of additional revisions to be shown, one per line.
137           Use this instead of explicitly specifying a <revision range> if the
138           set of commits to show may vary between refreshes.
139
140       --select-commit=<ref>
141           Select the specified commit after loading the graph. Default
142           behavior is equivalent to specifying --select-commit=HEAD.
143

EXAMPLES

145       gitk v2.6.12.. include/scsi drivers/scsi
146           Show the changes since version v2.6.12 that changed any file in the
147           include/scsi or drivers/scsi subdirectories
148
149       gitk --since="2 weeks ago" -- gitk
150           Show the changes during the last two weeks to the file gitk. The
151           "--" is necessary to avoid confusion with the branch named gitk
152
153       gitk --max-count=100 --all -- Makefile
154           Show at most 100 changes made to the file Makefile. Instead of only
155           looking for changes in the current branch look in all branches.
156

FILES

158       User configuration and preferences are stored at:
159
160       ·   $XDG_CONFIG_HOME/git/gitk if it exists, otherwise
161
162       ·   $HOME/.gitk if it exists
163
164       If neither of the above exist then $XDG_CONFIG_HOME/git/gitk is created
165       and used by default. If $XDG_CONFIG_HOME is not set it defaults to
166       $HOME/.config in all cases.
167

HISTORY

169       Gitk was the first graphical repository browser. It’s written in
170       tcl/tk.
171
172       gitk is actually maintained as an independent project, but stable
173       versions are distributed as part of the Git suite for the convenience
174       of end users.
175
176       gitk-git/ comes from Paul Mackerras’s gitk project:
177
178           git://ozlabs.org/~paulus/gitk
179

SEE ALSO

181       qgit(1)
182           A repository browser written in C++ using Qt.
183
184       tig(1)
185           A minimal repository browser and Git tool output highlighter
186           written in C using Ncurses.
187

GIT

189       Part of the git(1) suite
190
191
192
193Git 2.18.1                        05/14/2019                           GITK(1)
Impressum