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', 'format:<string>'
7 and 'tformat:<string>'. When '<format>' is none of the above,
8 and has '%placeholder' in it, it acts as if
9 '--pretty=tformat:<format>' were given.
11 See the "PRETTY FORMATS" section for some additional details for each
12 format. When '=<format>' part is omitted, it defaults to 'medium'.
14 Note: you can specify the default pretty format in the repository
15 configuration (see linkgit:git-config[1]).
18 Instead of showing the full 40-byte hexadecimal commit object
19 name, show only a partial prefix. Non default number of
20 digits can be specified with "--abbrev=<n>" (which also modifies
21 diff output, if it is displayed).
23 This should make "--pretty=oneline" a whole lot more readable for
24 people using 80-column terminals.
27 Show the full 40-byte hexadecimal commit object name. This negates
28 `--abbrev-commit` and those options which imply it such as
29 "--oneline". It also overrides the 'log.abbrevCommit' variable.
32 This is a shorthand for "--pretty=oneline --abbrev-commit"
35 --encoding=<encoding>::
36 The commit objects record the encoding used for the log message
37 in their encoding header; this option can be used to tell the
38 command to re-code the commit log message in the encoding
39 preferred by the user. For non plumbing commands this
43 Show the notes (see linkgit:git-notes[1]) that annotate the
44 commit, when showing the commit log message. This is the default
45 for `git log`, `git show` and `git whatchanged` commands when
46 there is no `--pretty`, `--format`, or `--oneline` option given
49 By default, the notes shown are from the notes refs listed in the
50 'core.notesRef' and 'notes.displayRef' variables (or corresponding
51 environment overrides). See linkgit:git-config[1] for more details.
53 With an optional '<ref>' argument, show this notes ref instead of the
54 default notes ref(s). The ref is taken to be in `refs/notes/` if it
57 Multiple --notes options can be combined to control which notes are
58 being displayed. Examples: "--notes=foo" will show only notes from
59 "refs/notes/foo"; "--notes=foo --notes" will show both notes from
60 "refs/notes/foo" and from the default notes ref(s).
63 Do not show notes. This negates the above `--notes` option, by
64 resetting the list of notes refs from which notes are shown.
65 Options are parsed in the order given on the command line, so e.g.
66 "--notes --notes=foo --no-notes --notes=bar" will only show notes
67 from "refs/notes/bar".
69 --show-notes[=<ref>]::
70 --[no-]standard-notes::
71 These options are deprecated. Use the above --notes/--no-notes
75 Check the validity of a signed commit object by passing the signature
76 to `gpg --verify` and show the output.