Documentation/pretty-options.txt

   1 --pretty[=<format>]::
   2 --format=<format>::
   3
   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.
  10 +
  11 See the "PRETTY FORMATS" section for some additional details for each
  12 format.  When '=<format>' part is omitted, it defaults to 'medium'.
  13 +
  14 Note: you can specify the default pretty format in the repository
  15 configuration (see linkgit:git-config[1]).
  16
  17 --abbrev-commit::
  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).
  22 +
  23 This should make "--pretty=oneline" a whole lot more readable for
  24 people using 80-column terminals.
  25
  26 --no-abbrev-commit::
  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.
  30
  31 --oneline::
  32         This is a shorthand for "--pretty=oneline --abbrev-commit"
  33         used together.
  34
  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
  40         defaults to UTF-8. Note that if an object claims to be encoded
  41         in `X` and we are outputting in `X`, we will output the object
  42         verbatim; this means that invalid sequences in the original
  43         commit may be copied to the output.
  44
  45 ifndef::git-rev-list[]
  46 --notes[=<ref>]::
  47         Show the notes (see linkgit:git-notes[1]) that annotate the
  48         commit, when showing the commit log message.  This is the default
  49         for `git log`, `git show` and `git whatchanged` commands when
  50         there is no `--pretty`, `--format`, or `--oneline` option given
  51         on the command line.
  52 +
  53 By default, the notes shown are from the notes refs listed in the
  54 'core.notesRef' and 'notes.displayRef' variables (or corresponding
  55 environment overrides). See linkgit:git-config[1] for more details.
  56 +
  57 With an optional '<ref>' argument, show this notes ref instead of the
  58 default notes ref(s). The ref specifies the full refname when it begins
  59 with `refs/notes/`; when it begins with `notes/`, `refs/` and otherwise
  60 `refs/notes/` is prefixed to form a full name of the ref.
  61 +
  62 Multiple --notes options can be combined to control which notes are
  63 being displayed. Examples: "--notes=foo" will show only notes from
  64 "refs/notes/foo"; "--notes=foo --notes" will show both notes from
  65 "refs/notes/foo" and from the default notes ref(s).
  66
  67 --no-notes::
  68         Do not show notes. This negates the above `--notes` option, by
  69         resetting the list of notes refs from which notes are shown.
  70         Options are parsed in the order given on the command line, so e.g.
  71         "--notes --notes=foo --no-notes --notes=bar" will only show notes
  72         from "refs/notes/bar".
  73
  74 --show-notes[=<ref>]::
  75 --[no-]standard-notes::
  76         These options are deprecated. Use the above --notes/--no-notes
  77         options instead.
  78 endif::git-rev-list[]
  79
  80 --show-signature::
  81         Check the validity of a signed commit object by passing the signature
  82         to `gpg --verify` and show the output.