4 Pretty-print the contents of the commit logs in a given format,
5 where '<format>' can be one of 'oneline', 'short', 'medium',
6 'full', 'fuller', 'email', 'raw' and 'format:<string>'. See
7 the "PRETTY FORMATS" section for some additional details for each
8 format. When omitted, the format defaults to 'medium'.
10 Note: you can specify the default pretty format in the repository
11 configuration (see linkgit:git-config[1]).
14 Instead of showing the full 40-byte hexadecimal commit object
15 name, show only a partial prefix. Non default number of
16 digits can be specified with "--abbrev=<n>" (which also modifies
17 diff output, if it is displayed).
19 This should make "--pretty=oneline" a whole lot more readable for
20 people using 80-column terminals.
23 Show the full 40-byte hexadecimal commit object name. This negates
24 `--abbrev-commit` and those options which imply it such as
25 "--oneline". It also overrides the 'log.abbrevCommit' variable.
28 This is a shorthand for "--pretty=oneline --abbrev-commit"
31 --encoding=<encoding>::
32 The commit objects record the encoding used for the log message
33 in their encoding header; this option can be used to tell the
34 command to re-code the commit log message in the encoding
35 preferred by the user. For non plumbing commands this
36 defaults to UTF-8. Note that if an object claims to be encoded
37 in `X` and we are outputting in `X`, we will output the object
38 verbatim; this means that invalid sequences in the original
39 commit may be copied to the output.
42 Show the notes (see linkgit:git-notes[1]) that annotate the
43 commit, when showing the commit log message. This is the default
44 for `git log`, `git show` and `git whatchanged` commands when
45 there is no `--pretty`, `--format`, or `--oneline` option given
48 By default, the notes shown are from the notes refs listed in the
49 'core.notesRef' and 'notes.displayRef' variables (or corresponding
50 environment overrides). See linkgit:git-config[1] for more details.
52 With an optional '<ref>' argument, show this notes ref instead of the
53 default notes ref(s). The ref is taken to be in `refs/notes/` if it
56 Multiple --notes options can be combined to control which notes are
57 being displayed. Examples: "--notes=foo" will show only notes from
58 "refs/notes/foo"; "--notes=foo --notes" will show both notes from
59 "refs/notes/foo" and from the default notes ref(s).
62 Do not show notes. This negates the above `--notes` option, by
63 resetting the list of notes refs from which notes are shown.
64 Options are parsed in the order given on the command line, so e.g.
65 "--notes --notes=foo --no-notes --notes=bar" will only show notes
66 from "refs/notes/bar".
68 --show-notes[=<ref>]::
69 --[no-]standard-notes::
70 These options are deprecated. Use the above --notes/--no-notes
74 Check the validity of a signed commit object by passing the signature
75 to `gpg --verify` and show the output.