Documentation / gitk.txton commit Merge branch 'jc/index-extended-flags' (0a8eb7b)
   1gitk(1)
   2=======
   3
   4NAME
   5----
   6gitk - The git repository browser
   7
   8SYNOPSIS
   9--------
  10'gitk' [<option>...] [<revs>] [--] [<path>...]
  11
  12DESCRIPTION
  13-----------
  14Displays changes in a repository or a selected set of commits. This includes
  15visualizing the commit graph, showing information related to each commit, and
  16the files in the trees of each revision.
  17
  18Historically, gitk was the first repository browser. It's written in tcl/tk
  19and started off in a separate repository but was later merged into the main
  20git repository.
  21
  22OPTIONS
  23-------
  24To control which revisions to shown, the command takes options applicable to
  25the 'git-rev-list' command (see linkgit:git-rev-list[1]).
  26This manual page describes only the most
  27frequently used options.
  28
  29-n <number>::
  30--max-count=<number>::
  31
  32        Limits the number of commits to show.
  33
  34--since=<date>::
  35
  36        Show commits more recent than a specific date.
  37
  38--until=<date>::
  39
  40        Show commits older than a specific date.
  41
  42--all::
  43
  44        Show all branches.
  45
  46--merge::
  47
  48        After an attempt to merge stops with conflicts, show the commits on
  49        the history between two branches (i.e. the HEAD and the MERGE_HEAD)
  50        that modify the conflicted files.
  51
  52<revs>::
  53
  54        Limit the revisions to show. This can be either a single revision
  55        meaning show from the given revision and back, or it can be a range in
  56        the form "'<from>'..'<to>'" to show all revisions between '<from>' and
  57        back to '<to>'. Note, more advanced revision selection can be applied.
  58        For a more complete list of ways to spell object names, see
  59        "SPECIFYING REVISIONS" section in linkgit:git-rev-parse[1].
  60
  61<path>...::
  62
  63        Limit commits to the ones touching files in the given paths. Note, to
  64        avoid ambiguity wrt. revision names use "--" to separate the paths
  65        from any preceding options.
  66
  67Examples
  68--------
  69gitk v2.6.12.. include/scsi drivers/scsi::
  70
  71        Show as the changes since version 'v2.6.12' that changed any
  72        file in the include/scsi or drivers/scsi subdirectories
  73
  74gitk --since="2 weeks ago" \-- gitk::
  75
  76        Show the changes during the last two weeks to the file 'gitk'.
  77        The "--" is necessary to avoid confusion with the *branch* named
  78        'gitk'
  79
  80gitk --max-count=100 --all \-- Makefile::
  81
  82        Show at most 100 changes made to the file 'Makefile'. Instead of only
  83        looking for changes in the current branch look in all branches.
  84
  85Files
  86-----
  87Gitk creates the .gitk file in your $HOME directory to store preferences
  88such as display options, font, and colors.
  89
  90SEE ALSO
  91--------
  92'qgit(1)'::
  93        A repository browser written in C++ using Qt.
  94
  95'gitview(1)'::
  96        A repository browser written in Python using Gtk. It's based on
  97        'bzrk(1)' and distributed in the contrib area of the git repository.
  98
  99'tig(1)'::
 100        A minimal repository browser and git tool output highlighter written
 101        in C using Ncurses.
 102
 103Author
 104------
 105Written by Paul Mackerras <paulus@samba.org>.
 106
 107Documentation
 108--------------
 109Documentation by Junio C Hamano, Jonas Fonseca, and the git-list
 110<git@vger.kernel.org>.
 111
 112GIT
 113---
 114Part of the linkgit:git[1] suite