Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
GITK(1)				  Git Manual			       GITK(1)

       gitk - The Git repository browser

       gitk [<options>]	[<revision range>] [--]	[<path>...]

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

       To control which	revisions to show, gitk	supports most options
       applicable to the git rev-list command. It also supports	a few options
       applicable to the git diff-* commands to	control	how the	changes	each
       commit introduces are shown. Finally, it	supports some gitk-specific

       gitk generally only understands options with arguments in the sticked
       form (see gitcli(7)) due	to limitations in the command-line parser.

   rev-list options and	arguments
       This manual page	describes only the most	frequently used	options. See
       git-rev-list(1) for a complete list.

	   Show	all refs (branches, tags, etc.).

       --branches[=<pattern>], --tags[=<pattern>], --remotes[=<pattern>]
	   Pretend as if all the branches (tags, remote	branches, resp.) are
	   listed on the command line as _commit_. If _pattern_	is given,
	   limit refs to ones matching given shell glob. If pattern lacks ?,
	   *, or [, /* at the end is implied.

	   Show	commits	more recent than a specific date.

	   Show	commits	older than a specific date.

	   Sort	commits	by date	when possible.

	   After an attempt to merge stops with	conflicts, show	the commits on
	   the history between two branches (i.e. the HEAD and the MERGE_HEAD)
	   that	modify the conflicted files and	do not exist on	all the	heads
	   being merged.

	   Mark	which side of a	symmetric difference a commit is reachable
	   from. Commits from the left side are	prefixed with a	< symbol and
	   those from the right	with a > symbol.

	   When	filtering history with _path_..., does not prune some history.
	   (See	"History simplification" in git-log(1) for a more detailed

	   Additional option to	--full-history to remove some needless merges
	   from	the resulting history, as there	are no selected	commits
	   contributing	to this	merge. (See "History simplification" in	git-
	   log(1) for a	more detailed explanation.)

	   When	given a	range of commits to display (e.g.  commit1..commit2 or
	   commit2 ^commit1), only display commits that	exist directly on the
	   ancestry chain between the commit1 and commit2, i.e.	commits	that
	   are both descendants	of commit1, and	ancestors of commit2. (See
	   "History simplification" in git-log(1) for a	more detailed

       -L<start>,<end>:<file>, -L:<funcname>:<file>
	   Trace the evolution of the line range given by _start_,_end_, or by
	   the function	name regex _funcname_, within the _file_. You may not
	   give	any pathspec limiters. This is currently limited to a walk
	   starting from a single revision, i.e., you may only give zero or
	   one positive	revision arguments, and	_start_	and _end_ (or
	   _funcname_) must exist in the starting revision. You	can specify
	   this	option more than once. Implies --patch.	Patch output can be
	   suppressed using --no-patch,	but other diff formats (namely --raw,
	   --numstat, --shortstat, --dirstat, --summary, --name-only,
	   --name-status, --check) are not currently implemented.

	   _start_ and _end_ can take one of these forms:

	   o   number

	       If _start_ or _end_ is a	number,	it specifies an	absolute line
	       number (lines count from	1).

	   o   /regex/

	       This form will use the first line matching the given POSIX
	       regex. If _start_ is a regex, it	will search from the end of
	       the previous -L range, if any, otherwise	from the start of
	       file. If	_start_	is ^/regex/, it	will search from the start of
	       file. If	_end_ is a regex, it will search starting at the line
	       given by	_start_.

	   o   +offset or -offset

	       This is only valid for _end_ and	will specify a number of lines
	       before or after the line	given by _start_.

	   If :<funcname> is given in place of _start_ and _end_, it is	a
	   regular expression that denotes the range from the first funcname
	   line	that matches _funcname_, up to the next	funcname line.
	   :<funcname> searches	from the end of	the previous -L	range, if any,
	   otherwise from the start of file.  ^:<funcname> searches from the
	   start of file. The function names are determined in the same	way as
	   git diff works out patch hunk headers (see Defining a custom
	   hunk-header in gitattributes(5)).

       <revision range>
	   Limit the revisions to show.	This can be either a single revision
	   meaning show	from the given revision	and back, or it	can be a range
	   in the form "_from_.._to_" to show all revisions between _from_ and
	   back	to _to_. Note, more advanced revision selection	can be
	   applied. For	a more complete	list of	ways to	spell object names,
	   see gitrevisions(7).

	   Limit commits to the	ones touching files in the given paths.	Note,
	   to avoid ambiguity with respect to revision names use "--" to
	   separate the	paths from any preceding options.

   gitk-specific options
	   Command to be run each time gitk has	to determine the revision
	   range to show. The command is expected to print on its standard
	   output a list of additional revisions to be shown, one per line.
	   Use this instead of explicitly specifying a _revision range_	if the
	   set of commits to show may vary between refreshes.

	   Select the specified	commit after loading the graph.	Default
	   behavior is equivalent to specifying	--select-commit=HEAD.

       gitk v2.6.12.. include/scsi drivers/scsi
	   Show	the changes since version v2.6.12 that changed any file	in the
	   include/scsi	or drivers/scsi	subdirectories

       gitk --since="2 weeks ago" -- gitk
	   Show	the changes during the last two	weeks to the file gitk.	The
	   "--"	is necessary to	avoid confusion	with the branch	named gitk

       gitk --max-count=100 --all -- Makefile
	   Show	at most	100 changes made to the	file Makefile. Instead of only
	   looking for changes in the current branch look in all branches.

       User configuration and preferences are stored at:

       o   $XDG_CONFIG_HOME/git/gitk if	it exists, otherwise

       o   $HOME/.gitk if it exists

       If neither of the above exist then $XDG_CONFIG_HOME/git/gitk is created
       and used	by default. If $XDG_CONFIG_HOME	is not set it defaults to
       $HOME/.config in	all cases.

       Gitk was	the first graphical repository browser.	It's written in

       gitk is actually	maintained as an independent project, but stable
       versions	are distributed	as part	of the Git suite for the convenience
       of end users.

       gitk-git/ comes from Paul Mackerras's gitk project:


	   A repository	browser	written	in C++ using Qt.

	   A minimal repository	browser	and Git	tool output highlighter
	   written in C	using Ncurses.

       Part of the git(1) suite

Git 2.35.1			  01/28/2022			       GITK(1)


Want to link to this manual page? Use this URL:

home | help