gitk(1) [debian man page]

GITK(1) 							    Git Manual								   GITK(1)

NAME

       gitk - The git repository browser

SYNOPSIS

       gitk [<option>...] [<revs>] [--] [<path>...]

DESCRIPTION

       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.

OPTIONS

       To control which revisions to show, the command takes options applicable to the git rev-list command (see git-rev-list(1)). This manual
       page describes only the most frequently used options.

       -n <number>, --max-count=<number>
	   Limits the number of commits to show.

       --since=<date>
	   Show commits more recent than a specific date.

       --until=<date>
	   Show commits older than a specific date.

       --all
	   Show all branches.

       --merge
	   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.

       --argscmd=<command>
	   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.

       --select-commit=<ref>
	   Automatically select the specified commit after loading the graph. Default behavior is equivalent to specifying --select-commit=HEAD.

       <revs>
	   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).

       <path>...
	   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.

EXAMPLES

       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.

FILES

       Gitk creates the .gitk file in your $HOME directory to store preferences such as display options, font, and colors.

SEE ALSO

       qgit(1)
	   A repository browser written in C++ using Qt.

       gitview(1)
	   A repository browser written in Python using Gtk. It's based on bzrk(1) and distributed in the contrib area of the git repository.

       tig(1)
	   A minimal repository browser and git tool output highlighter written in C using Ncurses.

GIT

       Part of the git(1) suite

Git 1.7.10.4							    11/24/2012								   GITK(1)

GIT-GUI(1)							    Git Manual								GIT-GUI(1)

NAME

       git-gui - A portable graphical interface to Git

SYNOPSIS

       git gui [<command>] [arguments]

DESCRIPTION

       A Tcl/Tk based graphical user interface to Git. git gui focuses on allowing users to make changes to their repository by making new
       commits, amending existing ones, creating branches, performing local merges, and fetching/pushing to remote repositories.

       Unlike gitk, git gui focuses on commit generation and single file annotation and does not show project history. It does however supply menu
       actions to start a gitk session from within git gui.

       git gui is known to work on all popular UNIX systems, Mac OS X, and Windows (under both Cygwin and MSYS). To the extent possible OS
       specific user interface guidelines are followed, making git gui a fairly native interface for users.

COMMANDS

       blame
	   Start a blame viewer on the specified file on the given version (or working directory if not specified).

       browser
	   Start a tree browser showing all files in the specified commit (or HEAD by default). Files selected through the browser are opened in
	   the blame viewer.

       citool
	   Start git gui and arrange to make exactly one commit before exiting and returning to the shell. The interface is limited to only commit
	   actions, slightly reducing the application's startup time and simplifying the menubar.

       version
	   Display the currently running version of git gui.

EXAMPLES

       git gui blame Makefile
	   Show the contents of the file Makefile in the current working directory, and provide annotations for both the original author of each
	   line, and who moved the line to its current location. The uncommitted file is annotated, and uncommitted changes (if any) are
	   explicitly attributed to Not Yet Committed.

       git gui blame v0.99.8 Makefile
	   Show the contents of Makefile in revision v0.99.8 and provide annotations for each line. Unlike the above example the file is read from
	   the object database and not the working directory.

       git gui blame --line=100 Makefile
	   Loads annotations as described above and automatically scrolls the view to center on line 100.

       git gui citool
	   Make one commit and return to the shell when it is complete. This command returns a non-zero exit code if the window was closed in any
	   way other than by making a commit.

       git gui citool --amend
	   Automatically enter the Amend Last Commit mode of the interface.

       git gui citool --nocommit
	   Behave as normal citool, but instead of making a commit simply terminate with a zero exit code. It still checks that the index does not
	   contain any unmerged entries, so you can use it as a GUI version of git-mergetool(1)

       git citool
	   Same as git gui citool (above).

       git gui browser maint
	   Show a browser for the tree of the maint branch. Files selected in the browser can be viewed with the internal blame viewer.

SEE ALSO

       gitk(1)
	   The git repository browser. Shows branches, commit history and file differences. gitk is the utility started by git gui's Repository
	   Visualize actions.

OTHER

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

       A git gui development repository can be obtained from:

	   git clone git://repo.or.cz/git-gui.git

       or

	   git clone http://repo.or.cz/r/git-gui.git

       or browsed online at http://repo.or.cz/w/git-gui.git/.

GIT

       Part of the git(1) suite

Git 1.7.10.4							    11/24/2012								GIT-GUI(1)