2006-02-07 11:47:47 +00:00
|
|
|
git-show(1)
|
|
|
|
|
===========
|
|
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
2006-12-14 10:31:05 +00:00
|
|
|
git-show - Show various types of objects
|
2006-02-07 11:47:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
2011-07-02 02:38:26 +00:00
|
|
|
[verse]
|
2008-06-30 06:09:04 +00:00
|
|
|
'git show' [options] <object>...
|
2006-02-07 11:47:47 +00:00
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
2006-12-14 10:31:05 +00:00
|
|
|
Shows one or more objects (blobs, trees, tags and commits).
|
|
|
|
|
|
|
|
|
|
For commits it shows the log message and textual diff. It also
|
|
|
|
|
presents the merge commit in a special format as produced by
|
2010-01-09 23:33:00 +00:00
|
|
|
'git diff-tree --cc'.
|
2006-12-14 10:31:05 +00:00
|
|
|
|
|
|
|
|
For tags, it shows the tag message and the referenced objects.
|
|
|
|
|
|
2010-01-09 23:33:00 +00:00
|
|
|
For trees, it shows the names (equivalent to 'git ls-tree'
|
2015-05-13 05:01:38 +00:00
|
|
|
with --name-only).
|
2006-12-14 10:31:05 +00:00
|
|
|
|
|
|
|
|
For plain blobs, it shows the plain contents.
|
2006-02-07 11:47:47 +00:00
|
|
|
|
2010-01-09 23:33:00 +00:00
|
|
|
The command takes options applicable to the 'git diff-tree' command to
|
2007-02-08 23:22:21 +00:00
|
|
|
control how the changes the commit introduces are shown.
|
|
|
|
|
|
2006-02-07 11:47:47 +00:00
|
|
|
This manual page describes only the most frequently used options.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
OPTIONS
|
|
|
|
|
-------
|
2008-07-30 09:33:43 +00:00
|
|
|
<object>...::
|
|
|
|
|
The names of objects to show.
|
2007-01-18 02:08:09 +00:00
|
|
|
For a more complete list of ways to spell object names, see
|
2010-10-11 16:03:32 +00:00
|
|
|
"SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
|
2006-02-07 11:47:47 +00:00
|
|
|
|
2007-05-13 23:25:45 +00:00
|
|
|
include::pretty-options.txt[]
|
|
|
|
|
|
|
|
|
|
|
2006-11-21 23:49:15 +00:00
|
|
|
include::pretty-formats.txt[]
|
2006-02-07 11:47:47 +00:00
|
|
|
|
2006-12-14 10:31:05 +00:00
|
|
|
|
2013-07-16 08:05:38 +00:00
|
|
|
COMMON DIFF OPTIONS
|
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
|
|
:git-log: 1
|
|
|
|
|
include::diff-options.txt[]
|
|
|
|
|
|
|
|
|
|
include::diff-generate-patch.txt[]
|
|
|
|
|
|
|
|
|
|
|
2006-12-14 10:31:05 +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 show v1.0.0`::
|
2006-12-30 10:21:48 +00:00
|
|
|
Shows the tag `v1.0.0`, along with the object the tags
|
|
|
|
|
points at.
|
2006-12-14 10:31:05 +00:00
|
|
|
|
docs: stop using asciidoc no-inline-literal
In asciidoc 7, backticks like `foo` produced a typographic
effect, but did not otherwise affect the syntax. In asciidoc
8, backticks introduce an "inline literal" inside which markup
is not interpreted. To keep compatibility with existing
documents, asciidoc 8 has a "no-inline-literal" attribute to
keep the old behavior. We enabled this so that the
documentation could be built on either version.
It has been several years now, and asciidoc 7 is no longer
in wide use. We can now decide whether or not we want
inline literals on their own merits, which are:
1. The source is much easier to read when the literal
contains punctuation. You can use `master~1` instead
of `master{tilde}1`.
2. They are less error-prone. Because of point (1), we
tend to make mistakes and forget the extra layer of
quoting.
This patch removes the no-inline-literal attribute from the
Makefile and converts every use of backticks in the
documentation to an inline literal (they must be cleaned up,
or the example above would literally show "{tilde}" in the
output).
Problematic sites were found by grepping for '`.*[{\\]' and
examined and fixed manually. The results were then verified
by comparing the output of "html2text" on the set of
generated html pages. Doing so revealed that in addition to
making the source more readable, this patch fixes several
formatting bugs:
- HTML rendering used the ellipsis character instead of
literal "..." in code examples (like "git log A...B")
- some code examples used the right-arrow character
instead of '->' because they failed to quote
- api-config.txt did not quote tilde, and the resulting
HTML contained a bogus snippet like:
<tt><sub></tt> foo <tt></sub>bar</tt>
which caused some parsers to choke and omit whole
sections of the page.
- git-commit.txt confused ``foo`` (backticks inside a
literal) with ``foo'' (matched double-quotes)
- mentions of `A U Thor <author@example.com>` used to
erroneously auto-generate a mailto footnote for
author@example.com
- the description of --word-diff=plain incorrectly showed
the output as "[-removed-] and {added}", not "{+added+}".
- using "prime" notation like:
commit `C` and its replacement `C'`
confused asciidoc into thinking that everything between
the first backtick and the final apostrophe were meant
to be inside matched quotes
- asciidoc got confused by the escaping of some of our
asterisks. In particular,
`credential.\*` and `credential.<url>.\*`
properly escaped the asterisk in the first case, but
literally passed through the backslash in the second
case.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-26 08:51:57 +00:00
|
|
|
`git show v1.0.0^{tree}`::
|
2006-12-14 10:31:05 +00:00
|
|
|
Shows the tree pointed to by the tag `v1.0.0`.
|
|
|
|
|
|
docs: stop using asciidoc no-inline-literal
In asciidoc 7, backticks like `foo` produced a typographic
effect, but did not otherwise affect the syntax. In asciidoc
8, backticks introduce an "inline literal" inside which markup
is not interpreted. To keep compatibility with existing
documents, asciidoc 8 has a "no-inline-literal" attribute to
keep the old behavior. We enabled this so that the
documentation could be built on either version.
It has been several years now, and asciidoc 7 is no longer
in wide use. We can now decide whether or not we want
inline literals on their own merits, which are:
1. The source is much easier to read when the literal
contains punctuation. You can use `master~1` instead
of `master{tilde}1`.
2. They are less error-prone. Because of point (1), we
tend to make mistakes and forget the extra layer of
quoting.
This patch removes the no-inline-literal attribute from the
Makefile and converts every use of backticks in the
documentation to an inline literal (they must be cleaned up,
or the example above would literally show "{tilde}" in the
output).
Problematic sites were found by grepping for '`.*[{\\]' and
examined and fixed manually. The results were then verified
by comparing the output of "html2text" on the set of
generated html pages. Doing so revealed that in addition to
making the source more readable, this patch fixes several
formatting bugs:
- HTML rendering used the ellipsis character instead of
literal "..." in code examples (like "git log A...B")
- some code examples used the right-arrow character
instead of '->' because they failed to quote
- api-config.txt did not quote tilde, and the resulting
HTML contained a bogus snippet like:
<tt><sub></tt> foo <tt></sub>bar</tt>
which caused some parsers to choke and omit whole
sections of the page.
- git-commit.txt confused ``foo`` (backticks inside a
literal) with ``foo'' (matched double-quotes)
- mentions of `A U Thor <author@example.com>` used to
erroneously auto-generate a mailto footnote for
author@example.com
- the description of --word-diff=plain incorrectly showed
the output as "[-removed-] and {added}", not "{+added+}".
- using "prime" notation like:
commit `C` and its replacement `C'`
confused asciidoc into thinking that everything between
the first backtick and the final apostrophe were meant
to be inside matched quotes
- asciidoc got confused by the escaping of some of our
asterisks. In particular,
`credential.\*` and `credential.<url>.\*`
properly escaped the asterisk in the first case, but
literally passed through the backslash in the second
case.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-26 08:51:57 +00:00
|
|
|
`git show -s --format=%s v1.0.0^{commit}`::
|
2010-11-09 17:12:48 +00:00
|
|
|
Shows the subject of the commit pointed to by the
|
|
|
|
|
tag `v1.0.0`.
|
|
|
|
|
|
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 show next~10:Documentation/README`::
|
2006-12-14 10:31:05 +00:00
|
|
|
Shows the contents of the file `Documentation/README` as
|
|
|
|
|
they were current in the 10th last commit of the branch
|
|
|
|
|
`next`.
|
|
|
|
|
|
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 show master:Makefile master:t/Makefile`::
|
2006-12-14 10:31:05 +00:00
|
|
|
Concatenates the contents of said Makefiles in the head
|
|
|
|
|
of the branch `master`.
|
|
|
|
|
|
2006-12-30 10:22:38 +00:00
|
|
|
Discussion
|
|
|
|
|
----------
|
|
|
|
|
|
|
|
|
|
include::i18n.txt[]
|
|
|
|
|
|
2006-02-07 11:47:47 +00:00
|
|
|
GIT
|
|
|
|
|
---
|
2008-06-06 07:07:32 +00:00
|
|
|
Part of the linkgit:git[1] suite
|