4 If the commit is a merge, and if the pretty-format
5 is not 'oneline', 'email' or 'raw', an additional line is
6 inserted before the 'Author:' line. This line begins with
7 "Merge: " and the sha1s of ancestral commits are printed,
8 separated by spaces. Note that the listed commits may not
9 necessarily be the list of the *direct* parent commits if you
10 have limited your view of history: for example, if you are
11 only interested in changes related to a certain directory or
14 There are several built-in formats, and you can define
15 additional formats by setting a pretty.<name>
16 config option to either another format name, or a
17 'format:' string, as described below (see
18 linkgit:git-config[1]). Here are the details of the
25 This is designed to be as compact as possible.
58 AuthorDate: <author date>
60 CommitDate: <committer date>
71 Subject: [PATCH] <title line>
77 The 'raw' format shows the entire commit exactly as
78 stored in the commit object. Notably, the SHA1s are
79 displayed in full, regardless of whether --abbrev or
80 --no-abbrev are used, and 'parents' information show the
81 true parent commits, without taking grafts nor history
82 simplification into account.
86 The 'format:<string>' format allows you to specify which information
87 you want to show. It works a little bit like printf format,
88 with the notable exception that you get a newline with '%n'
91 E.g, 'format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"'
92 would show something like this:
95 The author of fe6e0ee was Junio C Hamano, 23 hours ago
96 The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<
100 The placeholders are:
103 - '%h': abbreviated commit hash
105 - '%t': abbreviated tree hash
106 - '%P': parent hashes
107 - '%p': abbreviated parent hashes
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 format
119 - '%cn': committer name
120 - '%cN': committer name (respecting .mailmap, see
121 linkgit:git-shortlog[1] or linkgit:git-blame[1])
122 - '%ce': committer email
123 - '%cE': committer email (respecting .mailmap, see
124 linkgit:git-shortlog[1] or linkgit:git-blame[1])
125 - '%cd': committer date
126 - '%cD': committer date, RFC2822 style
127 - '%cr': committer date, relative
128 - '%ct': committer date, UNIX timestamp
129 - '%ci': committer date, ISO 8601 format
130 - '%d': ref names, like the --decorate option of linkgit:git-log[1]
133 - '%f': sanitized subject line, suitable for a filename
135 - '%B': raw body (unwrapped subject and body)
137 - '%GG': raw verification message from GPG for a signed commit
138 - '%G?': show "G" for a Good signature, "B" for a Bad signature, "U" for a good,
139 untrusted signature and "N" for no signature
140 - '%GS': show the name of the signer for a signed commit
141 - '%GK': show the key used to sign a signed commit
142 - '%gD': reflog selector, e.g., `refs/stash@{1}`
143 - '%gd': shortened reflog selector, e.g., `stash@{1}`
144 - '%gn': reflog identity name
145 - '%gN': reflog identity name (respecting .mailmap, see
146 linkgit:git-shortlog[1] or linkgit:git-blame[1])
147 - '%ge': reflog identity email
148 - '%gE': reflog identity email (respecting .mailmap, see
149 linkgit:git-shortlog[1] or linkgit:git-blame[1])
150 - '%gs': reflog subject
151 - '%Cred': switch color to red
152 - '%Cgreen': switch color to green
153 - '%Cblue': switch color to blue
154 - '%Creset': reset color
155 - '%C(...)': color specification, as described in color.branch.* config option;
156 adding `auto,` at the beginning will emit color only when colors are
157 enabled for log output (by `color.diff`, `color.ui`, or `--color`, and
158 respecting the `auto` settings of the former if we are going to a
160 - '%m': left, right or boundary mark
163 - '%x00': print a byte from a hex code
164 - '%w([<w>[,<i1>[,<i2>]]])': switch line wrapping, like the -w option of
165 linkgit:git-shortlog[1].
167 NOTE: Some placeholders may depend on other options given to the
168 revision traversal engine. For example, the `%g*` reflog options will
169 insert an empty string unless we are traversing reflog entries (e.g., by
170 `git log -g`). The `%d` placeholder will use the "short" decoration
171 format if `--decorate` was not already provided on the command line.
173 If you add a `+` (plus sign) after '%' of a placeholder, a line-feed
174 is inserted immediately before the expansion if and only if the
175 placeholder expands to a non-empty string.
177 If you add a `-` (minus sign) after '%' of a placeholder, line-feeds that
178 immediately precede the expansion are deleted if and only if the
179 placeholder expands to an empty string.
181 If you add a ` ` (space) after '%' of a placeholder, a space
182 is inserted immediately before the expansion if and only if the
183 placeholder expands to a non-empty string.
187 The 'tformat:' format works exactly like 'format:', except that it
188 provides "terminator" semantics instead of "separator" semantics. In
189 other words, each commit has the message terminator character (usually a
190 newline) appended, rather than a separator placed between entries.
191 This means that the final entry of a single-line format will be properly
192 terminated with a new line, just as the "oneline" format does.
195 ---------------------
196 $ git log -2 --pretty=format:%h 4da45bef \
197 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
199 7134973 -- NO NEWLINE
201 $ git log -2 --pretty=tformat:%h 4da45bef \
202 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
205 ---------------------
207 In addition, any unrecognized string that has a `%` in it is interpreted
208 as if it has `tformat:` in front of it. For example, these two are
211 ---------------------
212 $ git log -2 --pretty=tformat:%h 4da45bef
213 $ git log -2 --pretty=%h 4da45bef
214 ---------------------