Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.12.1 → 2.13.1 no changes
- 2.12.0 02/24/17
- 2.10.2 → 2.11.2 no changes
- 2.10.1 10/03/16
- 2.9.4 → 2.10.0 no changes
- 2.9.3 08/12/16
- 2.4.2 → 2.9.2 no changes
- 2.4.1 05/13/15
- 2.4.0 04/30/15
- 2.3.9 → 2.3.10 no changes
- 2.3.8 05/11/15
- 2.1.1 → 2.3.7 no changes
- 2.1.0 08/15/14
- 2.0.1 → 2.0.5 no changes
- 2.0.0 05/28/14
- 1.9.1 → 1.9.5 no changes
- 1.9.0 02/14/14
- 18.104.22.168 → 22.214.171.124 no changes
- 1.8.5 11/27/13
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.
Historically, gitk was the first repository browser. It’s written in tcl/tk and started off in a separate repository but was later merged into the main git repository.
To control which revisions to show, the command takes options applicable to the git-rev-list command (see git-rev-list). This manual page describes only the most frequently used options.
- -n <number>
Limits the number of commits to show.
Show commits more recent than a specific date.
Show commits older than a specific date.
Show all branches.
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.
Command to be run each time gitk has to determine the list of <revs> to show. The command is expected to print on its standard output a list of additional revs to be shown, one per line. Use this instead of explicitly specifying <revs> if the set of commits to show may vary between refreshes.
Automatically select the specified commit after loading the graph. Default behavior is equivalent to specifying --select-commit=HEAD.
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 "SPECIFYING REVISIONS" section in git-rev-parse.
Limit commits to the ones touching files in the given paths. Note, to avoid ambiguity wrt. revision names use "--" to separate the paths from any preceding options.
- 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.
Gitk creates the .gitk file in your $HOME directory to store preferences such as display options, font, and colors.
Written by Paul Mackerras <firstname.lastname@example.org>.
Documentation by Junio C Hamano, Jonas Fonseca, and the git-list <email@example.com>.
Part of the git suite