2007-06-21 04:51:00 +00:00
|
|
|
git-gui(1)
|
|
|
|
|
==========
|
|
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
|
|
|
|
git-gui - A portable graphical interface to Git
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
2011-07-02 02:38:26 +00:00
|
|
|
[verse]
|
2007-06-21 04:51:00 +00:00
|
|
|
'git gui' [<command>] [arguments]
|
|
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
2010-01-09 23:33:00 +00:00
|
|
|
A Tcl/Tk based graphical user interface to Git. 'git gui' focuses
|
2007-06-21 04:51:00 +00:00
|
|
|
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.
|
|
|
|
|
|
2010-01-09 23:33:00 +00:00
|
|
|
Unlike 'gitk', 'git gui' focuses on commit generation
|
2008-06-30 18:56:34 +00:00
|
|
|
and single file annotation and does not show project history.
|
2008-07-03 05:49:55 +00:00
|
|
|
It does however supply menu actions to start a 'gitk' session from
|
2010-01-09 23:33:00 +00:00
|
|
|
within 'git gui'.
|
2007-06-21 04:51:00 +00:00
|
|
|
|
2010-01-09 23:33:00 +00:00
|
|
|
'git gui' is known to work on all popular UNIX systems, Mac OS X,
|
2007-06-21 04:51:00 +00:00
|
|
|
and Windows (under both Cygwin and MSYS). To the extent possible
|
2010-01-09 23:33:00 +00:00
|
|
|
OS specific user interface guidelines are followed, making 'git gui'
|
2007-06-21 04:51:00 +00:00
|
|
|
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
|
2017-01-12 21:32:40 +00:00
|
|
|
commit. Files selected through the
|
2007-06-21 04:51:00 +00:00
|
|
|
browser are opened in the blame viewer.
|
|
|
|
|
|
|
|
|
|
citool::
|
2010-01-09 23:33:00 +00:00
|
|
|
Start 'git gui' and arrange to make exactly one commit before
|
2007-06-21 04:51:00 +00:00
|
|
|
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::
|
2010-01-09 23:33:00 +00:00
|
|
|
Display the currently running version of 'git gui'.
|
2007-06-21 04:51:00 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
Examples
|
|
|
|
|
--------
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git gui blame Makefile`::
|
2007-06-21 04:51:00 +00:00
|
|
|
|
|
|
|
|
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'.
|
|
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git gui blame v0.99.8 Makefile`::
|
2007-06-21 04:51:00 +00:00
|
|
|
|
|
|
|
|
Show the contents of 'Makefile' in revision 'v0.99.8'
|
2008-07-03 05:03:54 +00:00
|
|
|
and provide annotations for each line. Unlike the above
|
2007-06-21 04:51:00 +00:00
|
|
|
example the file is read from the object database and not
|
|
|
|
|
the working directory.
|
|
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git gui blame --line=100 Makefile`::
|
2008-11-13 17:28:49 +00:00
|
|
|
|
|
|
|
|
Loads annotations as described above and automatically
|
|
|
|
|
scrolls the view to center on line '100'.
|
|
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git gui citool`::
|
2007-06-21 04:51:00 +00:00
|
|
|
|
|
|
|
|
Make one commit and return to the shell when it is complete.
|
2008-11-13 17:28:49 +00:00
|
|
|
This command returns a non-zero exit code if the window was
|
|
|
|
|
closed in any way other than by making a commit.
|
|
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git gui citool --amend`::
|
2008-11-13 17:28:49 +00:00
|
|
|
|
|
|
|
|
Automatically enter the 'Amend Last Commit' mode of
|
|
|
|
|
the interface.
|
|
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git gui citool --nocommit`::
|
2008-11-13 17:28:49 +00:00
|
|
|
|
|
|
|
|
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 linkgit:git-mergetool[1]
|
2007-06-21 04:51:00 +00:00
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git citool`::
|
2007-06-21 04:51:00 +00:00
|
|
|
|
2008-07-03 06:06:23 +00:00
|
|
|
Same as `git gui citool` (above).
|
2007-06-21 04:51:00 +00:00
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git gui browser maint`::
|
2007-06-21 04:51:00 +00:00
|
|
|
|
|
|
|
|
Show a browser for the tree of the 'maint' branch. Files
|
|
|
|
|
selected in the browser can be viewed with the internal
|
|
|
|
|
blame viewer.
|
|
|
|
|
|
2008-05-28 23:55:27 +00:00
|
|
|
SEE ALSO
|
2007-06-21 04:51:00 +00:00
|
|
|
--------
|
2008-05-28 23:55:27 +00:00
|
|
|
linkgit:gitk[1]::
|
2013-01-21 19:17:53 +00:00
|
|
|
The Git repository browser. Shows branches, commit history
|
2007-06-21 04:51:00 +00:00
|
|
|
and file differences. gitk is the utility started by
|
2010-01-09 23:33:00 +00:00
|
|
|
'git gui''s Repository Visualize actions.
|
2007-06-21 04:51:00 +00:00
|
|
|
|
|
|
|
|
Other
|
|
|
|
|
-----
|
2010-01-09 23:33:00 +00:00
|
|
|
'git gui' is actually maintained as an independent project, but stable
|
2007-08-24 00:44:13 +00:00
|
|
|
versions are distributed as part of the Git suite for the convenience
|
2007-06-21 04:51:00 +00:00
|
|
|
of end users.
|
|
|
|
|
|
2010-01-09 23:33:00 +00:00
|
|
|
A 'git gui' development repository can be obtained from:
|
2007-06-21 04:51:00 +00:00
|
|
|
|
|
|
|
|
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
|
|
|
|
|
---
|
2008-06-06 07:07:32 +00:00
|
|
|
Part of the linkgit:git[1] suite
|
