1GIT-SHOW(1) Git Manual GIT-SHOW(1)
2
6 git-show - Show various types of objects
7
9 git show [options] <object>...
10
13 Shows one or more objects (blobs, trees, tags and commits).
14 For commits it shows the log message and textual diff. It also presents
16 the merge commit in a special format as produced by git diff-tree --cc.
17 For tags, it shows the tag message and the referenced objects.
19 For trees, it shows the names (equivalent to git ls-tree with
21 --name-only).
22 For plain blobs, it shows the plain contents.
24 The command takes options applicable to the git diff-tree command to
26 control how the changes the commit introduces are shown.
27 This manual page describes only the most frequently used options.
29
31 <object>...
32 The names of objects to show. For a more complete list of ways to
33 spell object names, see "SPECIFYING REVISIONS" section in
34 gitrevisions(7).
35 --pretty[=<format>], --format=<format>
37 Pretty-print the contents of the commit logs in a given format,
38 where <format> can be one of oneline, short, medium, full, fuller,
39 email, raw and format:<string>. See the "PRETTY FORMATS" section
40 for some additional details for each format. When omitted, the
41 format defaults to medium.
42 Note: you can specify the default pretty format in the repository
44 configuration (see git-config(1)).
45 --abbrev-commit
47 Instead of showing the full 40-byte hexadecimal commit object name,
48 show only a partial prefix. Non default number of digits can be
49 specified with "--abbrev=<n>" (which also modifies diff output, if
50 it is displayed).
51 This should make "--pretty=oneline" a whole lot more readable for
53 people using 80-column terminals.
54 --no-abbrev-commit
56 Show the full 40-byte hexadecimal commit object name. This negates
57 --abbrev-commit and those options which imply it such as
58 "--oneline". It also overrides the log.abbrevCommit variable.
59 --oneline
61 This is a shorthand for "--pretty=oneline --abbrev-commit" used
62 together.
63 --encoding[=<encoding>]
65 The commit objects record the encoding used for the log message in
66 their encoding header; this option can be used to tell the command
67 to re-code the commit log message in the encoding preferred by the
68 user. For non plumbing commands this defaults to UTF-8.
69 --notes[=<ref>]
71 Show the notes (see git-notes(1)) that annotate the commit, when
72 showing the commit log message. This is the default for git log,
73 git show and git whatchanged commands when there is no --pretty,
74 --format nor --oneline option given on the command line.
75 By default, the notes shown are from the notes refs listed in the
77 core.notesRef and notes.displayRef variables (or corresponding
78 environment overrides). See git-config(1) for more details.
79 With an optional <ref> argument, show this notes ref instead of the
81 default notes ref(s). The ref is taken to be in refs/notes/ if it
82 is not qualified.
83 Multiple --notes options can be combined to control which notes are
85 being displayed. Examples: "--notes=foo" will show only notes from
86 "refs/notes/foo"; "--notes=foo --notes" will show both notes from
87 "refs/notes/foo" and from the default notes ref(s).
88 --no-notes
90 Do not show notes. This negates the above --notes option, by
91 resetting the list of notes refs from which notes are shown.
92 Options are parsed in the order given on the command line, so e.g.
93 "--notes --notes=foo --no-notes --notes=bar" will only show notes
94 from "refs/notes/bar".
95 --show-notes[=<ref>], --[no-]standard-notes
97 These options are deprecated. Use the above --notes/--no-notes
98 options instead.
99 --show-signature
101 Check the validity of a signed commit object by passing the
102 signature to gpg --verify and show the output.
103
105 If the commit is a merge, and if the pretty-format is not oneline,
106 email or raw, an additional line is inserted before the Author: line.
107 This line begins with "Merge: " and the sha1s of ancestral commits are
108 printed, separated by spaces. Note that the listed commits may not
109 necessarily be the list of the direct parent commits if you have
110 limited your view of history: for example, if you are only interested
111 in changes related to a certain directory or file.
112 There are several built-in formats, and you can define additional
114 formats by setting a pretty.<name> config option to either another
115 format name, or a format: string, as described below (see git-
116 config(1)). Here are the details of the built-in formats:
117 · oneline
119 <sha1> <title line>
121 This is designed to be as compact as possible.
123 · short
125 commit <sha1>
127 Author: <author>
128 <title line>
130 · medium
132 commit <sha1>
134 Author: <author>
135 Date: <author date>
136 <title line>
138 <full commit message>
140 · full
142 commit <sha1>
144 Author: <author>
145 Commit: <committer>
146 <title line>
148 <full commit message>
150 · fuller
152 commit <sha1>
154 Author: <author>
155 AuthorDate: <author date>
156 Commit: <committer>
157 CommitDate: <committer date>
158 <title line>
160 <full commit message>
162 · email
164 From <sha1> <date>
166 From: <author>
167 Date: <author date>
168 Subject: [PATCH] <title line>
169 <full commit message>
171 · raw
173 The raw format shows the entire commit exactly as stored in the
175 commit object. Notably, the SHA-1s are displayed in full,
176 regardless of whether --abbrev or --no-abbrev are used, and parents
177 information show the true parent commits, without taking grafts nor
178 history simplification into account.
179 · format:<string>
181 The format:<string> format allows you to specify which information
183 you want to show. It works a little bit like printf format, with
184 the notable exception that you get a newline with %n instead of \n.
185 E.g, format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"
187 would show something like this:
188 The author of fe6e0ee was Junio C Hamano, 23 hours ago
190 The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<
191 The placeholders are:
193 · %H: commit hash
195 · %h: abbreviated commit hash
197 · %T: tree hash
199 · %t: abbreviated tree hash
201 · %P: parent hashes
203 · %p: abbreviated parent hashes
205 · %an: author name
207 · %aN: author name (respecting .mailmap, see git-shortlog(1) or
209 git-blame(1))
210 · %ae: author email
212 · %aE: author email (respecting .mailmap, see git-shortlog(1) or
214 git-blame(1))
215 · %ad: author date (format respects --date= option)
217 · %aD: author date, RFC2822 style
219 · %ar: author date, relative
221 · %at: author date, UNIX timestamp
223 · %ai: author date, ISO 8601 format
225 · %cn: committer name
227 · %cN: committer name (respecting .mailmap, see git-shortlog(1)
229 or git-blame(1))
230 · %ce: committer email
232 · %cE: committer email (respecting .mailmap, see git-shortlog(1)
234 or git-blame(1))
235 · %cd: committer date
237 · %cD: committer date, RFC2822 style
239 · %cr: committer date, relative
241 · %ct: committer date, UNIX timestamp
243 · %ci: committer date, ISO 8601 format
245 · %d: ref names, like the --decorate option of git-log(1)
247 · %e: encoding
249 · %s: subject
251 · %f: sanitized subject line, suitable for a filename
253 · %b: body
255 · %B: raw body (unwrapped subject and body)
257 · %N: commit notes
259 · %GG: raw verification message from GPG for a signed commit
261 · %G?: show "G" for a Good signature, "B" for a Bad signature,
263 "U" for a good, untrusted signature and "N" for no signature
264 · %GS: show the name of the signer for a signed commit
266 · %GK: show the key used to sign a signed commit
268 · %gD: reflog selector, e.g., refs/stash@{1}
270 · %gd: shortened reflog selector, e.g., stash@{1}
272 · %gn: reflog identity name
274 · %gN: reflog identity name (respecting .mailmap, see git-
276 shortlog(1) or git-blame(1))
277 · %ge: reflog identity email
279 · %gE: reflog identity email (respecting .mailmap, see git-
281 shortlog(1) or git-blame(1))
282 · %gs: reflog subject
284 · %Cred: switch color to red
286 · %Cgreen: switch color to green
288 · %Cblue: switch color to blue
290 · %Creset: reset color
292 · %C(...): color specification, as described in color.branch.*
294 config option; adding auto, at the beginning will emit color
295 only when colors are enabled for log output (by color.diff,
296 color.ui, or --color, and respecting the auto settings of the
297 former if we are going to a terminal). auto alone (i.e.
298 %C(auto)) will turn on auto coloring on the next placeholders
299 until the color is switched again.
300 · %m: left, right or boundary mark
302 · %n: newline
304 · %%: a raw %
306 · %x00: print a byte from a hex code
308 · %w([<w>[,<i1>[,<i2>]]]): switch line wrapping, like the -w
310 option of git-shortlog(1).
311 · %<(<N>[,trunc|ltrunc|mtrunc]): make the next placeholder take
313 at least N columns, padding spaces on the right if necessary.
314 Optionally truncate at the beginning (ltrunc), the middle
315 (mtrunc) or the end (trunc) if the output is longer than N
316 columns. Note that truncating only works correctly with N >= 2.
317 · %<|(<N>): make the next placeholder take at least until Nth
319 columns, padding spaces on the right if necessary
320 · %>(<N>), %>|(<N>): similar to %<(<N>), %<|(<N>) respectively,
322 but padding spaces on the left
323 · %>>(<N>), %>>|(<N>): similar to %>(<N>), %>|(<N>) respectively,
325 except that if the next placeholder takes more spaces than
326 given and there are spaces on its left, use those spaces
327 · %><(<N>), %><|(<N>): similar to % <(<N>), %<|(<N>)
329 respectively, but padding both sides (i.e. the text is
330 centered)
331 Note
333 Some placeholders may depend on other options given to the revision
334 traversal engine. For example, the %g* reflog options will insert
335 an empty string unless we are traversing reflog entries (e.g., by
336 git log -g). The %d placeholder will use the "short" decoration
337 format if --decorate was not already provided on the command line.
338 If you add a + (plus sign) after % of a placeholder, a line-feed is
340 inserted immediately before the expansion if and only if the
341 placeholder expands to a non-empty string.
342 If you add a - (minus sign) after % of a placeholder, line-feeds that
344 immediately precede the expansion are deleted if and only if the
345 placeholder expands to an empty string.
346 If you add a ` ` (space) after % of a placeholder, a space is inserted
348 immediately before the expansion if and only if the placeholder expands
349 to a non-empty string.
350 · tformat:
352 The tformat: format works exactly like format:, except that it
354 provides "terminator" semantics instead of "separator" semantics.
355 In other words, each commit has the message terminator character
356 (usually a newline) appended, rather than a separator placed
357 between entries. This means that the final entry of a single-line
358 format will be properly terminated with a new line, just as the
359 "oneline" format does. For example:
360 $ git log -2 --pretty=format:%h 4da45bef \
362 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
363 4da45be
364 7134973 -- NO NEWLINE
365 $ git log -2 --pretty=tformat:%h 4da45bef \
367 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
368 4da45be
369 7134973
370 In addition, any unrecognized string that has a % in it is
372 interpreted as if it has tformat: in front of it. For example,
373 these two are equivalent:
374 $ git log -2 --pretty=tformat:%h 4da45bef
376 $ git log -2 --pretty=%h 4da45bef
377
380 git show v1.0.0
381 Shows the tag v1.0.0, along with the object the tags points at.
382 git show v1.0.0^{tree}
384 Shows the tree pointed to by the tag v1.0.0.
385 git show -s --format=%s v1.0.0^{commit}
387 Shows the subject of the commit pointed to by the tag v1.0.0.
388 git show next~10:Documentation/README
390 Shows the contents of the file Documentation/README as they were
391 current in the 10th last commit of the branch next.
392 git show master:Makefile master:t/Makefile
394 Concatenates the contents of said Makefiles in the head of the
395 branch master.
396
398 At the core level, Git is character encoding agnostic.
399 · The pathnames recorded in the index and in the tree objects are
401 treated as uninterpreted sequences of non-NUL bytes. What
402 readdir(2) returns are what are recorded and compared with the data
403 Git keeps track of, which in turn are expected to be what lstat(2)
404 and creat(2) accepts. There is no such thing as pathname encoding
405 translation.
406 · The contents of the blob objects are uninterpreted sequences of
408 bytes. There is no encoding translation at the core level.
409 · The commit log messages are uninterpreted sequences of non-NUL
411 bytes.
412 Although we encourage that the commit log messages are encoded in
414 UTF-8, both the core and Git Porcelain are designed not to force UTF-8
415 on projects. If all participants of a particular project find it more
416 convenient to use legacy encodings, Git does not forbid it. However,
417 there are a few things to keep in mind.
418 1. git commit and git commit-tree issues a warning if the commit log
420 message given to it does not look like a valid UTF-8 string, unless
421 you explicitly say your project uses a legacy encoding. The way to
422 say this is to have i18n.commitencoding in .git/config file, like
423 this:
424 [i18n]
426 commitencoding = ISO-8859-1
427 Commit objects created with the above setting record the value of
429 i18n.commitencoding in its encoding header. This is to help other
430 people who look at them later. Lack of this header implies that the
431 commit log message is encoded in UTF-8.
432 2. git log, git show, git blame and friends look at the encoding
434 header of a commit object, and try to re-code the log message into
435 UTF-8 unless otherwise specified. You can specify the desired
436 output encoding with i18n.logoutputencoding in .git/config file,
437 like this:
438 [i18n]
440 logoutputencoding = ISO-8859-1
441 If you do not have this configuration variable, the value of
443 i18n.commitencoding is used instead.
444 Note that we deliberately chose not to re-code the commit log message
446 when a commit is made to force UTF-8 at the commit object level,
447 because re-coding to UTF-8 is not necessarily a reversible operation.
448
450 Part of the git(1) suite
451Git 1.8.3.1 11/19/2018 GIT-SHOW(1)