1PRETTY FORMATS 2-------------- 3 4If the commit is a merge, and if the pretty-format 5is not 'oneline', 'email' or 'raw', an additional line is 6inserted before the 'Author:' line. This line begins with 7"Merge: " and the sha1s of ancestral commits are printed, 8separated by spaces. Note that the listed commits may not 9necessarily be the list of the *direct* parent commits if you 10have limited your view of history: for example, if you are 11only interested in changes related to a certain directory or 12file. 13 14There are several built-in formats, and you can define 15additional formats by setting a pretty.<name> 16config option to either another format name, or a 17'format:' string, as described below (see 18linkgit:git-config[1]). Here are the details of the 19built-in formats: 20 21* 'oneline' 22 23 <sha1> <title line> 24+ 25This is designed to be as compact as possible. 26 27* 'short' 28 29 commit <sha1> 30 Author: <author> 31 32 <title line> 33 34* 'medium' 35 36 commit <sha1> 37 Author: <author> 38 Date: <author date> 39 40 <title line> 41 42 <full commit message> 43 44* 'full' 45 46 commit <sha1> 47 Author: <author> 48 Commit: <committer> 49 50 <title line> 51 52 <full commit message> 53 54* 'fuller' 55 56 commit <sha1> 57 Author: <author> 58 AuthorDate: <author date> 59 Commit: <committer> 60 CommitDate: <committer date> 61 62 <title line> 63 64 <full commit message> 65 66* 'email' 67 68 From <sha1> <date> 69 From: <author> 70 Date: <author date> 71 Subject: [PATCH] <title line> 72 73 <full commit message> 74 75* 'raw' 76+ 77The 'raw' format shows the entire commit exactly as 78stored in the commit object. Notably, the SHA-1s are 79displayed in full, regardless of whether --abbrev or 80--no-abbrev are used, and 'parents' information show the 81true parent commits, without taking grafts or history 82simplification into account. 83 84* 'format:<string>' 85+ 86The 'format:<string>' format allows you to specify which information 87you want to show. It works a little bit like printf format, 88with the notable exception that you get a newline with '%n' 89instead of '\n'. 90+ 91E.g, 'format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"' 92would show something like this: 93+ 94------- 95The author of fe6e0ee was Junio C Hamano, 23 hours ago 96The title was >>t4119: test autocomputing -p<n> for traditional diff input.<< 97 98-------- 99+ 100The placeholders are: 101 102- '%H': commit hash 103- '%h': abbreviated commit hash 104- '%T': tree hash 105- '%t': abbreviated tree hash 106- '%P': parent hashes 107- '%p': abbreviated parent hashes 108- '%an': author name 109- '%aN': author name (respecting .mailmap, see linkgit:git-shortlog[1] 110 or linkgit:git-blame[1]) 111- '%ae': author email 112- '%aE': author email (respecting .mailmap, see 113 linkgit:git-shortlog[1] or linkgit:git-blame[1]) 114- '%ad': author date (format respects --date= option) 115- '%aD': author date, RFC2822 style 116- '%ar': author date, relative 117- '%at': author date, UNIX timestamp 118- '%ai': author date, ISO 8601-like format 119- '%aI': author date, strict ISO 8601 format 120- '%cn': committer name 121- '%cN': committer name (respecting .mailmap, see 122 linkgit:git-shortlog[1] or linkgit:git-blame[1]) 123- '%ce': committer email 124- '%cE': committer email (respecting .mailmap, see 125 linkgit:git-shortlog[1] or linkgit:git-blame[1]) 126- '%cd': committer date (format respects --date= option) 127- '%cD': committer date, RFC2822 style 128- '%cr': committer date, relative 129- '%ct': committer date, UNIX timestamp 130- '%ci': committer date, ISO 8601-like format 131- '%cI': committer date, strict ISO 8601 format 132- '%d': ref names, like the --decorate option of linkgit:git-log[1] 133- '%e': encoding 134- '%s': subject 135- '%f': sanitized subject line, suitable for a filename 136- '%b': body 137- '%B': raw body (unwrapped subject and body) 138- '%N': commit notes 139- '%GG': raw verification message from GPG for a signed commit 140- '%G?': show "G" for a Good signature, "B" for a Bad signature, "U" for a good, 141 untrusted signature and "N" for no signature 142- '%GS': show the name of the signer for a signed commit 143- '%GK': show the key used to sign a signed commit 144- '%gD': reflog selector, e.g., `refs/stash@{1}` 145- '%gd': shortened reflog selector, e.g., `stash@{1}` 146- '%gn': reflog identity name 147- '%gN': reflog identity name (respecting .mailmap, see 148 linkgit:git-shortlog[1] or linkgit:git-blame[1]) 149- '%ge': reflog identity email 150- '%gE': reflog identity email (respecting .mailmap, see 151 linkgit:git-shortlog[1] or linkgit:git-blame[1]) 152- '%gs': reflog subject 153- '%Cred': switch color to red 154- '%Cgreen': switch color to green 155- '%Cblue': switch color to blue 156- '%Creset': reset color 157- '%C(...)': color specification, as described in color.branch.* config option; 158 adding `auto,` at the beginning will emit color only when colors are 159 enabled for log output (by `color.diff`, `color.ui`, or `--color`, and 160 respecting the `auto` settings of the former if we are going to a 161 terminal). `auto` alone (i.e. `%C(auto)`) will turn on auto coloring 162 on the next placeholders until the color is switched again. 163- '%m': left, right or boundary mark 164- '%n': newline 165- '%%': a raw '%' 166- '%x00': print a byte from a hex code 167- '%w([<w>[,<i1>[,<i2>]]])': switch line wrapping, like the -w option of 168 linkgit:git-shortlog[1]. 169- '%<(<N>[,trunc|ltrunc|mtrunc])': make the next placeholder take at 170 least N columns, padding spaces on the right if necessary. 171 Optionally truncate at the beginning (ltrunc), the middle (mtrunc) 172 or the end (trunc) if the output is longer than N columns. 173 Note that truncating only works correctly with N >= 2. 174- '%<|(<N>)': make the next placeholder take at least until Nth 175 columns, padding spaces on the right if necessary 176- '%>(<N>)', '%>|(<N>)': similar to '%<(<N>)', '%<|(<N>)' 177 respectively, but padding spaces on the left 178- '%>>(<N>)', '%>>|(<N>)': similar to '%>(<N>)', '%>|(<N>)' 179 respectively, except that if the next placeholder takes more spaces 180 than given and there are spaces on its left, use those spaces 181- '%><(<N>)', '%><|(<N>)': similar to '% <(<N>)', '%<|(<N>)' 182 respectively, but padding both sides (i.e. the text is centered) 183 184NOTE: Some placeholders may depend on other options given to the 185revision traversal engine. For example, the `%g*` reflog options will 186insert an empty string unless we are traversing reflog entries (e.g., by 187`git log -g`). The `%d` placeholder will use the "short" decoration 188format if `--decorate` was not already provided on the command line. 189 190If you add a `+` (plus sign) after '%' of a placeholder, a line-feed 191is inserted immediately before the expansion if and only if the 192placeholder expands to a non-empty string. 193 194If you add a `-` (minus sign) after '%' of a placeholder, line-feeds that 195immediately precede the expansion are deleted if and only if the 196placeholder expands to an empty string. 197 198If you add a ` ` (space) after '%' of a placeholder, a space 199is inserted immediately before the expansion if and only if the 200placeholder expands to a non-empty string. 201 202* 'tformat:' 203+ 204The 'tformat:' format works exactly like 'format:', except that it 205provides "terminator" semantics instead of "separator" semantics. In 206other words, each commit has the message terminator character (usually a 207newline) appended, rather than a separator placed between entries. 208This means that the final entry of a single-line format will be properly 209terminated with a new line, just as the "oneline" format does. 210For example: 211+ 212--------------------- 213$ git log -2 --pretty=format:%h 4da45bef \ 214 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/' 2154da45be 2167134973 -- NO NEWLINE 217 218$ git log -2 --pretty=tformat:%h 4da45bef \ 219 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/' 2204da45be 2217134973 222--------------------- 223+ 224In addition, any unrecognized string that has a `%` in it is interpreted 225as if it has `tformat:` in front of it. For example, these two are 226equivalent: 227+ 228--------------------- 229$ git log -2 --pretty=tformat:%h 4da45bef 230$ git log -2 --pretty=%h 4da45bef 231---------------------