.\"     Title: git-show
.\"    Author: 
.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
.\"      Date: 01/14/2011
.\"    Manual: Git Manual
.\"    Source: Git 1.5.6.5
.\"
.TH "GIT\-SHOW" "1" "01/14/2011" "Git 1\&.5\&.6\&.5" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.SH "NAME"
git-show \- Show various types of objects
.SH "SYNOPSIS"
\fIgit\-show\fR [options] <object>\&...
.sp
.SH "DESCRIPTION"
Shows one or more objects (blobs, trees, tags and commits)\&.
.sp
For commits it shows the log message and textual diff\&. It also presents the merge commit in a special format as produced by \fIgit\-diff\-tree \-\-cc\fR\&.
.sp
For tags, it shows the tag message and the referenced objects\&.
.sp
For trees, it shows the names (equivalent to \fBgit-ls-tree\fR(1) with \-\-name\-only)\&.
.sp
For plain blobs, it shows the plain contents\&.
.sp
The command takes options applicable to the \fBgit-diff-tree\fR(1) command to control how the changes the commit introduces are shown\&.
.sp
This manual page describes only the most frequently used options\&.
.sp
.SH "OPTIONS"
.PP
<object>
.RS 4
The name of the object to show\&. For a more complete list of ways to spell object names, see "SPECIFYING REVISIONS" section in
\fBgit-rev-parse\fR(1)\&.
.RE
.PP
\-\-pretty[=\fI<format>\fR]
.RS 4
Pretty\-print the contents of the commit logs in a given format, where
\fI<format>\fR
can be one of
\fIoneline\fR,
\fIshort\fR,
\fImedium\fR,
\fIfull\fR,
\fIfuller\fR,
\fIemail\fR,
\fIraw\fR
and
\fIformat:<string>\fR\&. When omitted, the format defaults to
\fImedium\fR\&.
.sp
Note: you can specify the default pretty format in the repository configuration (see
\fBgit-config\fR(1))\&.
.RE
.PP
\-\-abbrev\-commit
.RS 4
Instead of showing the full 40\-byte hexadecimal commit object name, show only handful hexdigits prefix\&. Non default number of digits can be specified with "\-\-abbrev=<n>" (which also modifies diff output, if it is displayed)\&.
.sp
This should make "\-\-pretty=oneline" a whole lot more readable for people using 80\-column terminals\&.
.RE
.PP
\-\-encoding[=<encoding>]
.RS 4
The commit objects record the encoding used for the log message in their encoding header; this option can be used to tell the command to re\-code the commit log message in the encoding preferred by the user\&. For non plumbing commands this defaults to UTF\-8\&.
.RE
.SH "PRETTY FORMATS"
If the commit is a merge, and if the pretty\-format is not \fIoneline\fR, \fIemail\fR or \fIraw\fR, an additional line is inserted before the \fIAuthor:\fR line\&. This line begins with "Merge: " and the sha1s of ancestral commits are printed, separated by spaces\&. Note that the listed commits may not necessarily be the list of the \fBdirect\fR parent commits if you have limited your view of history: for example, if you are only interested in changes related to a certain directory or file\&.
.sp
Here are some additional details for each format:
.sp
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fIoneline\fR
.sp
.RS 4
.nf
<sha1> <title line>
.fi
.RE
This is designed to be as compact as possible\&.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fIshort\fR
.sp
.RS 4
.nf
commit <sha1>
Author: <author>
.fi
.RE
.sp
.RS 4
.nf
<title line>
.fi
.RE
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fImedium\fR
.sp
.RS 4
.nf
commit <sha1>
Author: <author>
Date: <author date>
.fi
.RE
.sp
.RS 4
.nf
<title line>
.fi
.RE
.sp
.RS 4
.nf
<full commit message>
.fi
.RE
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fIfull\fR
.sp
.RS 4
.nf
commit <sha1>
Author: <author>
Commit: <committer>
.fi
.RE
.sp
.RS 4
.nf
<title line>
.fi
.RE
.sp
.RS 4
.nf
<full commit message>
.fi
.RE
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fIfuller\fR
.sp
.RS 4
.nf
commit <sha1>
Author: <author>
AuthorDate: <author date>
Commit: <committer>
CommitDate: <committer date>
.fi
.RE
.sp
.RS 4
.nf
<title line>
.fi
.RE
.sp
.RS 4
.nf
<full commit message>
.fi
.RE
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fIemail\fR
.sp
.RS 4
.nf
From <sha1> <date>
From: <author>
Date: <author date>
Subject: [PATCH] <title line>
.fi
.RE
.sp
.RS 4
.nf
<full commit message>
.fi
.RE
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fIraw\fR
.sp
The
\fIraw\fR
format shows the entire commit exactly as stored in the commit object\&. Notably, the SHA1s are displayed in full, regardless of whether \-\-abbrev or \-\-no\-abbrev are used, and
\fIparents\fR
information show the true parent commits, without taking grafts nor history simplification into account\&.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fIformat:\fR
.sp
The
\fIformat:\fR
format allows you to specify which information you want to show\&. It works a little bit like printf format, with the notable exception that you get a newline with
\fI%n\fR
instead of
\fI\en\fR\&.
.sp
E\&.g,
\fIformat:"The author of %h was %an, %ar%nThe title was >>%s<<%n"\fR
would show something like this:
.sp
.RS 4
.nf
The author of fe6e0ee was Junio C Hamano, 23 hours ago
The title was >>t4119: test autocomputing \-p<n> for traditional diff input\&.<<
.fi
.RE
The placeholders are:
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%H\fR: commit hash
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%h\fR: abbreviated commit hash
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%T\fR: tree hash
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%t\fR: abbreviated tree hash
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%P\fR: parent hashes
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%p\fR: abbreviated parent hashes
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%an\fR: author name
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%aN\fR: author name (respecting \&.mailmap)
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%ae\fR: author email
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%ad\fR: author date
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%aD\fR: author date, RFC2822 style
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%ar\fR: author date, relative
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%at\fR: author date, UNIX timestamp
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%ai\fR: author date, ISO 8601 format
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%cn\fR: committer name
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%cN\fR: committer name (respecting \&.mailmap)
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%ce\fR: committer email
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%cd\fR: committer date
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%cD\fR: committer date, RFC2822 style
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%cr\fR: committer date, relative
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%ct\fR: committer date, UNIX timestamp
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%ci\fR: committer date, ISO 8601 format
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%e\fR: encoding
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%s\fR: subject
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%b\fR: body
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%Cred\fR: switch color to red
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%Cgreen\fR: switch color to green
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%Cblue\fR: switch color to blue
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%Creset\fR: reset color
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%m\fR: left, right or boundary mark
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%n\fR: newline
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fI%x00\fR: print a byte from a hex code
.RE
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'
\fItformat:\fR
.sp
The
\fItformat:\fR
format works exactly like
\fIformat:\fR, except that it provides "terminator" semantics instead of "separator" semantics\&. In other words, each commit has the message terminator character (usually a newline) appended, rather than a separator placed between entries\&. This means that the final entry of a single\-line format will be properly terminated with a new line, just as the "oneline" format does\&. For example:
.sp
.RS 4
.nf
$ git log \-2 \-\-pretty=format:%h 4da45bef \e
  | perl \-pe \'$_ \&.= " \-\- NO NEWLINE\en" unless /\en/\'
4da45be
7134973 \-\- NO NEWLINE

$ git log \-2 \-\-pretty=tformat:%h 4da45bef \e
  | perl \-pe \'$_ \&.= " \-\- NO NEWLINE\en" unless /\en/\'
4da45be
7134973
.fi
.RE
.RE
.SH "EXAMPLES"
.PP
git show v1\&.0\&.0
.RS 4
Shows the tag
v1\&.0\&.0, along with the object the tags points at\&.
.RE
.PP
git show v1\&.0\&.0^{tree}
.RS 4
Shows the tree pointed to by the tag
v1\&.0\&.0\&.
.RE
.PP
git show next~10:Documentation/README
.RS 4
Shows the contents of the file
Documentation/README
as they were current in the 10th last commit of the branch
next\&.
.RE
.PP
git show master:Makefile master:t/Makefile
.RS 4
Concatenates the contents of said Makefiles in the head of the branch
master\&.
.RE
.SH "DISCUSSION"
At the core level, git is character encoding agnostic\&.
.sp
.sp
.RS 4
\h'-04'\(bu\h'+03'The pathnames recorded in the index and in the tree objects are treated as uninterpreted sequences of non\-NUL bytes\&. What readdir(2) returns are what are recorded and compared with the data git keeps track of, which in turn are expected to be what lstat(2) and creat(2) accepts\&. There is no such thing as pathname encoding translation\&.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'The contents of the blob objects are uninterpreted sequence of bytes\&. There is no encoding translation at the core level\&.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+03'The commit log messages are uninterpreted sequence of non\-NUL bytes\&.
.RE
Although we encourage that the commit log messages are encoded in UTF\-8, both the core and git Porcelain are designed not to force UTF\-8 on projects\&. If all participants of a particular project find it more convenient to use legacy encodings, git does not forbid it\&. However, there are a few things to keep in mind\&.
.sp
.sp
.RS 4
\h'-04' 1.\h'+02'
git\-commit\-tree
(hence,
git\-commit
which uses it) issues a warning if the commit log message given to it does not look like a valid UTF\-8 string, unless you explicitly say your project uses a legacy encoding\&. The way to say this is to have i18n\&.commitencoding in
\&.git/config
file, like this:
.sp
.RS 4
.nf
[i18n]
        commitencoding = ISO\-8859\-1
.fi
.RE
Commit objects created with the above setting record the value of
i18n\&.commitencoding
in its
encoding
header\&. This is to help other people who look at them later\&. Lack of this header implies that the commit log message is encoded in UTF\-8\&.
.RE
.sp
.RS 4
\h'-04' 2.\h'+02'
git\-log,
git\-show
and friends looks at the
encoding
header of a commit object, and tries to re\-code the log message into UTF\-8 unless otherwise specified\&. You can specify the desired output encoding with
i18n\&.logoutputencoding
in
\&.git/config
file, like this:
.sp
.RS 4
.nf
[i18n]
        logoutputencoding = ISO\-8859\-1
.fi
.RE
If you do not have this configuration variable, the value of
i18n\&.commitencoding
is used instead\&.
.RE
Note that we deliberately chose not to re\-code the commit log message when a commit is made to force UTF\-8 at the commit object level, because re\-coding to UTF\-8 is not necessarily a reversible operation\&.
.sp
.SH "AUTHOR"
Written by Linus Torvalds <\fItorvalds@osdl\&.org\fR\&[1]> and Junio C Hamano <\fIgitster@pobox\&.com\fR\&[2]>\&. Significantly enhanced by Johannes Schindelin <\fIJohannes\&.Schindelin@gmx\&.de\fR\&[3]>\&.
.sp
.SH "DOCUMENTATION"
Documentation by David Greaves, Petr Baudis and the git\-list <\fIgit@vger\&.kernel\&.org\fR\&[4]>\&.
.sp
.SH "GIT"
Part of the \fBgit\fR(1) suite
.sp
.SH "NOTES"
.IP " 1." 4
torvalds@osdl.org
.RS 4
\%mailto:torvalds@osdl.org
.RE
.IP " 2." 4
gitster@pobox.com
.RS 4
\%mailto:gitster@pobox.com
.RE
.IP " 3." 4
Johannes.Schindelin@gmx.de
.RS 4
\%mailto:Johannes.Schindelin@gmx.de
.RE
.IP " 4." 4
git@vger.kernel.org
.RS 4
\%mailto:git@vger.kernel.org
.RE