logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

git-rev-list.1 (83267B)

    

  1. '\" t
  2. .\"     Title: git-rev-list
  3. .\"    Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
  4. .\" Generator: DocBook XSL Stylesheets v1.79.2 <http://docbook.sf.net/>
  5. .\"      Date: 2025-03-14
  6. .\"    Manual: Git Manual
  7. .\"    Source: Git 2.49.0
  8. .\"  Language: English
  9. .\"
  10. .TH "GIT\-REV\-LIST" "1" "2025-03-14" "Git 2\&.49\&.0" "Git Manual"
  11. .\" -----------------------------------------------------------------
  12. .\" * Define some portability stuff
  13. .\" -----------------------------------------------------------------
  14. .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  15. .\" http://bugs.debian.org/507673
  16. .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
  17. .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  18. .ie \n(.g .ds Aq \(aq
  19. .el       .ds Aq '
  20. .\" -----------------------------------------------------------------
  21. .\" * set default formatting
  22. .\" -----------------------------------------------------------------
  23. .\" disable hyphenation
  24. .nh
  25. .\" disable justification (adjust text to left margin only)
  26. .ad l
  27. .\" -----------------------------------------------------------------
  28. .\" * MAIN CONTENT STARTS HERE *
  29. .\" -----------------------------------------------------------------
  30. .SH "NAME"
  31. git-rev-list \- Lists commit objects in reverse chronological order
  32. .SH "SYNOPSIS"
  33. .sp
  34. .nf
  35. \fIgit rev\-list\fR [<options>] <commit>\&...\: [\-\-] [<path>\&...\:]
  36. .fi
  37. .SH "DESCRIPTION"
  38. .sp
  39. List commits that are reachable by following the \fBparent\fR links from the given commit(s), but exclude commits that are reachable from the one(s) given with a \fI^\fR in front of them\&. The output is given in reverse chronological order by default\&.
  40. .sp
  41. You can think of this as a set operation\&. Commits reachable from any of the commits given on the command line form a set, and then commits reachable from any of the ones given with \fI^\fR in front are subtracted from that set\&. The remaining commits are what comes out in the command\(cqs output\&. Various other options and paths parameters can be used to further limit the result\&.
  42. .sp
  43. Thus, the following command:
  44. .sp
  45. .if n \{\
  46. .RS 4
  47. .\}
  48. .nf
  49. $ git rev\-list foo bar ^baz
  50. .fi
  51. .if n \{\
  52. .RE
  53. .\}
  54. .sp
  55. means "list all the commits which are reachable from \fIfoo\fR or \fIbar\fR, but not from \fIbaz\fR"\&.
  56. .sp
  57. A special notation "\fI<commit1>\fR\&.\&.\fI<commit2>\fR" can be used as a short\-hand for "^\fI<commit1>\fR \fI<commit2>\fR"\&. For example, either of the following may be used interchangeably:
  58. .sp
  59. .if n \{\
  60. .RS 4
  61. .\}
  62. .nf
  63. $ git rev\-list origin\&.\&.HEAD
  64. $ git rev\-list HEAD ^origin
  65. .fi
  66. .if n \{\
  67. .RE
  68. .\}
  69. .sp
  70. Another special notation is "\fI<commit1>\fR\&...\:\fI<commit2>\fR" which is useful for merges\&. The resulting set of commits is the symmetric difference between the two operands\&. The following two commands are equivalent:
  71. .sp
  72. .if n \{\
  73. .RS 4
  74. .\}
  75. .nf
  76. $ git rev\-list A B \-\-not $(git merge\-base \-\-all A B)
  77. $ git rev\-list A\&.\&.\&.B
  78. .fi
  79. .if n \{\
  80. .RE
  81. .\}
  82. .sp
  83. \fIrev\-list\fR is an essential Git command, since it provides the ability to build and traverse commit ancestry graphs\&. For this reason, it has a lot of different options that enable it to be used by commands as different as \fIgit bisect\fR and \fIgit repack\fR\&.
  84. .SH "OPTIONS"
  85. .SS "Commit Limiting"
  86. .sp
  87. Besides specifying a range of commits that should be listed using the special notations explained in the description, additional commit limiting may be applied\&.
  88. .sp
  89. Using more options generally further limits the output (e\&.g\&. \fB\-\-since=\fR\fI<date1>\fR limits to commits newer than \fI<date1>\fR, and using it with \fB\-\-grep=\fR\fI<pattern>\fR further limits to commits whose log message has a line that matches \fI<pattern>\fR), unless otherwise noted\&.
  90. .sp
  91. Note that these are applied before commit ordering and formatting options, such as \fB\-\-reverse\fR\&.
  92. .PP
  93. \-<number>, \-n <number>, \-\-max\-count=<number>
  94. .RS 4
  95. Limit the number of commits to output\&.
  96. .RE
  97. .PP
  98. \-\-skip=<number>
  99. .RS 4
  100. Skip
  101. \fInumber\fR
  102. commits before starting to show the commit output\&.
  103. .RE
  104. .PP
  105. \-\-since=<date>, \-\-after=<date>
  106. .RS 4
  107. Show commits more recent than a specific date\&.
  108. .RE
  109. .PP
  110. \-\-since\-as\-filter=<date>
  111. .RS 4
  112. Show all commits more recent than a specific date\&. This visits all commits in the range, rather than stopping at the first commit which is older than a specific date\&.
  113. .RE
  114. .PP
  115. \-\-until=<date>, \-\-before=<date>
  116. .RS 4
  117. Show commits older than a specific date\&.
  118. .RE
  119. .PP
  120. \-\-max\-age=<timestamp>, \-\-min\-age=<timestamp>
  121. .RS 4
  122. Limit the commits output to specified time range\&.
  123. .RE
  124. .PP
  125. \-\-author=<pattern>, \-\-committer=<pattern>
  126. .RS 4
  127. Limit the commits output to ones with author/committer header lines that match the specified pattern (regular expression)\&. With more than one
  128. \fB\-\-author=\fR\fI<pattern>\fR, commits whose author matches any of the given patterns are chosen (similarly for multiple
  129. \fB\-\-committer=\fR\fI<pattern>\fR)\&.
  130. .RE
  131. .PP
  132. \-\-grep\-reflog=<pattern>
  133. .RS 4
  134. Limit the commits output to ones with reflog entries that match the specified pattern (regular expression)\&. With more than one
  135. \fB\-\-grep\-reflog\fR, commits whose reflog message matches any of the given patterns are chosen\&. It is an error to use this option unless
  136. \fB\-\-walk\-reflogs\fR
  137. is in use\&.
  138. .RE
  139. .PP
  140. \-\-grep=<pattern>
  141. .RS 4
  142. Limit the commits output to ones with a log message that matches the specified pattern (regular expression)\&. With more than one
  143. \fB\-\-grep=\fR\fI<pattern>\fR, commits whose message matches any of the given patterns are chosen (but see
  144. \fB\-\-all\-match\fR)\&.
  145. .RE
  146. .PP
  147. \-\-all\-match
  148. .RS 4
  149. Limit the commits output to ones that match all given
  150. \fB\-\-grep\fR, instead of ones that match at least one\&.
  151. .RE
  152. .PP
  153. \-\-invert\-grep
  154. .RS 4
  155. Limit the commits output to ones with a log message that do not match the pattern specified with
  156. \fB\-\-grep=\fR\fI<pattern>\fR\&.
  157. .RE
  158. .PP
  159. \-i, \-\-regexp\-ignore\-case
  160. .RS 4
  161. Match the regular expression limiting patterns without regard to letter case\&.
  162. .RE
  163. .PP
  164. \-\-basic\-regexp
  165. .RS 4
  166. Consider the limiting patterns to be basic regular expressions; this is the default\&.
  167. .RE
  168. .PP
  169. \-E, \-\-extended\-regexp
  170. .RS 4
  171. Consider the limiting patterns to be extended regular expressions instead of the default basic regular expressions\&.
  172. .RE
  173. .PP
  174. \-F, \-\-fixed\-strings
  175. .RS 4
  176. Consider the limiting patterns to be fixed strings (don\(cqt interpret pattern as a regular expression)\&.
  177. .RE
  178. .PP
  179. \-P, \-\-perl\-regexp
  180. .RS 4
  181. Consider the limiting patterns to be Perl\-compatible regular expressions\&.
  182. .sp
  183. Support for these types of regular expressions is an optional compile\-time dependency\&. If Git wasn\(cqt compiled with support for them providing this option will cause it to die\&.
  184. .RE
  185. .PP
  186. \-\-remove\-empty
  187. .RS 4
  188. Stop when a given path disappears from the tree\&.
  189. .RE
  190. .PP
  191. \-\-merges
  192. .RS 4
  193. Print only merge commits\&. This is exactly the same as
  194. \fB\-\-min\-parents=2\fR\&.
  195. .RE
  196. .PP
  197. \-\-no\-merges
  198. .RS 4
  199. Do not print commits with more than one parent\&. This is exactly the same as
  200. \fB\-\-max\-parents=1\fR\&.
  201. .RE
  202. .PP
  203. \-\-min\-parents=<number>, \-\-max\-parents=<number>, \-\-no\-min\-parents, \-\-no\-max\-parents
  204. .RS 4
  205. Show only commits which have at least (or at most) that many parent commits\&. In particular,
  206. \fB\-\-max\-parents=1\fR
  207. is the same as
  208. \fB\-\-no\-merges\fR,
  209. \fB\-\-min\-parents=2\fR
  210. is the same as
  211. \fB\-\-merges\fR\&.
  212. \fB\-\-max\-parents=0\fR
  213. gives all root commits and
  214. \fB\-\-min\-parents=3\fR
  215. all octopus merges\&.
  216. .sp
  217. \fB\-\-no\-min\-parents\fR
  218. and
  219. \fB\-\-no\-max\-parents\fR
  220. reset these limits (to no limit) again\&. Equivalent forms are
  221. \fB\-\-min\-parents=0\fR
  222. (any commit has 0 or more parents) and
  223. \fB\-\-max\-parents=\-1\fR
  224. (negative numbers denote no upper limit)\&.
  225. .RE
  226. .PP
  227. \-\-first\-parent
  228. .RS 4
  229. When finding commits to include, follow only the first parent commit upon seeing a merge commit\&. This option can give a better overview when viewing the evolution of a particular topic branch, because merges into a topic branch tend to be only about adjusting to updated upstream from time to time, and this option allows you to ignore the individual commits brought in to your history by such a merge\&.
  230. .RE
  231. .PP
  232. \-\-exclude\-first\-parent\-only
  233. .RS 4
  234. When finding commits to exclude (with a
  235. \fI^\fR), follow only the first parent commit upon seeing a merge commit\&. This can be used to find the set of changes in a topic branch from the point where it diverged from the remote branch, given that arbitrary merges can be valid topic branch changes\&.
  236. .RE
  237. .PP
  238. \-\-not
  239. .RS 4
  240. Reverses the meaning of the
  241. \fI^\fR
  242. prefix (or lack thereof) for all following revision specifiers, up to the next
  243. \fB\-\-not\fR\&. When used on the command line before \-\-stdin, the revisions passed through stdin will not be affected by it\&. Conversely, when passed via standard input, the revisions passed on the command line will not be affected by it\&.
  244. .RE
  245. .PP
  246. \-\-all
  247. .RS 4
  248. Pretend as if all the refs in
  249. \fBrefs/\fR, along with
  250. \fBHEAD\fR, are listed on the command line as
  251. \fI<commit>\fR\&.
  252. .RE
  253. .PP
  254. \-\-branches[=<pattern>]
  255. .RS 4
  256. Pretend as if all the refs in
  257. \fBrefs/heads\fR
  258. are listed on the command line as
  259. \fI<commit>\fR\&. If
  260. \fI<pattern>\fR
  261. is given, limit branches to ones matching given shell glob\&. If pattern lacks
  262. \fI?\fR,
  263. \fI*\fR, or
  264. \fI[\fR,
  265. \fI/*\fR
  266. at the end is implied\&.
  267. .RE
  268. .PP
  269. \-\-tags[=<pattern>]
  270. .RS 4
  271. Pretend as if all the refs in
  272. \fBrefs/tags\fR
  273. are listed on the command line as
  274. \fI<commit>\fR\&. If
  275. \fI<pattern>\fR
  276. is given, limit tags to ones matching given shell glob\&. If pattern lacks
  277. \fI?\fR,
  278. \fI*\fR, or
  279. \fI[\fR,
  280. \fI/*\fR
  281. at the end is implied\&.
  282. .RE
  283. .PP
  284. \-\-remotes[=<pattern>]
  285. .RS 4
  286. Pretend as if all the refs in
  287. \fBrefs/remotes\fR
  288. are listed on the command line as
  289. \fI<commit>\fR\&. If
  290. \fI<pattern>\fR
  291. is given, limit remote\-tracking branches to ones matching given shell glob\&. If pattern lacks
  292. \fI?\fR,
  293. \fI*\fR, or
  294. \fI[\fR,
  295. \fI/*\fR
  296. at the end is implied\&.
  297. .RE
  298. .PP
  299. \-\-glob=<glob\-pattern>
  300. .RS 4
  301. Pretend as if all the refs matching shell glob
  302. \fI<glob\-pattern>\fR
  303. are listed on the command line as
  304. \fI<commit>\fR\&. Leading
  305. \fIrefs/\fR, is automatically prepended if missing\&. If pattern lacks
  306. \fI?\fR,
  307. \fI*\fR, or
  308. \fI[\fR,
  309. \fI/*\fR
  310. at the end is implied\&.
  311. .RE
  312. .PP
  313. \-\-exclude=<glob\-pattern>
  314. .RS 4
  315. Do not include refs matching
  316. \fI<glob\-pattern>\fR
  317. that the next
  318. \fB\-\-all\fR,
  319. \fB\-\-branches\fR,
  320. \fB\-\-tags\fR,
  321. \fB\-\-remotes\fR, or
  322. \fB\-\-glob\fR
  323. would otherwise consider\&. Repetitions of this option accumulate exclusion patterns up to the next
  324. \fB\-\-all\fR,
  325. \fB\-\-branches\fR,
  326. \fB\-\-tags\fR,
  327. \fB\-\-remotes\fR, or
  328. \fB\-\-glob\fR
  329. option (other options or arguments do not clear accumulated patterns)\&.
  330. .sp
  331. The patterns given should not begin with
  332. \fBrefs/heads\fR,
  333. \fBrefs/tags\fR, or
  334. \fBrefs/remotes\fR
  335. when applied to
  336. \fB\-\-branches\fR,
  337. \fB\-\-tags\fR, or
  338. \fB\-\-remotes\fR, respectively, and they must begin with
  339. \fBrefs/\fR
  340. when applied to
  341. \fB\-\-glob\fR
  342. or
  343. \fB\-\-all\fR\&. If a trailing
  344. \fI/*\fR
  345. is intended, it must be given explicitly\&.
  346. .RE
  347. .PP
  348. \-\-exclude\-hidden=[fetch|receive|uploadpack]
  349. .RS 4
  350. Do not include refs that would be hidden by
  351. \fBgit\-fetch\fR,
  352. \fBgit\-receive\-pack\fR
  353. or
  354. \fBgit\-upload\-pack\fR
  355. by consulting the appropriate
  356. \fBfetch\&.hideRefs\fR,
  357. \fBreceive\&.hideRefs\fR
  358. or
  359. \fBuploadpack\&.hideRefs\fR
  360. configuration along with
  361. \fBtransfer\&.hideRefs\fR
  362. (see
  363. \fBgit-config\fR(1))\&. This option affects the next pseudo\-ref option
  364. \fB\-\-all\fR
  365. or
  366. \fB\-\-glob\fR
  367. and is cleared after processing them\&.
  368. .RE
  369. .PP
  370. \-\-reflog
  371. .RS 4
  372. Pretend as if all objects mentioned by reflogs are listed on the command line as
  373. \fI<commit>\fR\&.
  374. .RE
  375. .PP
  376. \-\-alternate\-refs
  377. .RS 4
  378. Pretend as if all objects mentioned as ref tips of alternate repositories were listed on the command line\&. An alternate repository is any repository whose object directory is specified in
  379. \fBobjects/info/alternates\fR\&. The set of included objects may be modified by
  380. \fBcore\&.alternateRefsCommand\fR, etc\&. See
  381. \fBgit-config\fR(1)\&.
  382. .RE
  383. .PP
  384. \-\-single\-worktree
  385. .RS 4
  386. By default, all working trees will be examined by the following options when there are more than one (see
  387. \fBgit-worktree\fR(1)):
  388. \fB\-\-all\fR,
  389. \fB\-\-reflog\fR
  390. and
  391. \fB\-\-indexed\-objects\fR\&. This option forces them to examine the current working tree only\&.
  392. .RE
  393. .PP
  394. \-\-ignore\-missing
  395. .RS 4
  396. Upon seeing an invalid object name in the input, pretend as if the bad input was not given\&.
  397. .RE
  398. .PP
  399. \-\-stdin
  400. .RS 4
  401. In addition to getting arguments from the command line, read them from standard input as well\&. This accepts commits and pseudo\-options like
  402. \fB\-\-all\fR
  403. and
  404. \fB\-\-glob=\fR\&. When a
  405. \fB\-\-\fR
  406. separator is seen, the following input is treated as paths and used to limit the result\&. Flags like
  407. \fB\-\-not\fR
  408. which are read via standard input are only respected for arguments passed in the same way and will not influence any subsequent command line arguments\&.
  409. .RE
  410. .PP
  411. \-\-quiet
  412. .RS 4
  413. Don\(cqt print anything to standard output\&. This form is primarily meant to allow the caller to test the exit status to see if a range of objects is fully connected (or not)\&. It is faster than redirecting stdout to
  414. \fB/dev/null\fR
  415. as the output does not have to be formatted\&.
  416. .RE
  417. .PP
  418. \-\-disk\-usage, \-\-disk\-usage=human
  419. .RS 4
  420. Suppress normal output; instead, print the sum of the bytes used for on\-disk storage by the selected commits or objects\&. This is equivalent to piping the output into
  421. \fBgit\fR
  422. \fBcat\-file\fR
  423. \fB\-\-batch\-check=\fR\*(Aq%(\fBobjectsize:disk\fR)\*(Aq, except that it runs much faster (especially with
  424. \fB\-\-use\-bitmap\-index\fR)\&. See the
  425. \fBCAVEATS\fR
  426. section in
  427. \fBgit-cat-file\fR(1)
  428. for the limitations of what "on\-disk storage" means\&. With the optional value
  429. \fBhuman\fR, on\-disk storage size is shown in human\-readable string(e\&.g\&. 12\&.24 Kib, 3\&.50 Mib)\&.
  430. .RE
  431. .PP
  432. \-\-cherry\-mark
  433. .RS 4
  434. Like
  435. \fB\-\-cherry\-pick\fR
  436. (see below) but mark equivalent commits with
  437. \fB=\fR
  438. rather than omitting them, and inequivalent ones with
  439. \fB+\fR\&.
  440. .RE
  441. .PP
  442. \-\-cherry\-pick
  443. .RS 4
  444. Omit any commit that introduces the same change as another commit on the
  445. \(lqother side\(rq
  446. when the set of commits are limited with symmetric difference\&.
  447. .sp
  448. For example, if you have two branches,
  449. \fBA\fR
  450. and
  451. \fBB\fR, a usual way to list all commits on only one side of them is with
  452. \fB\-\-left\-right\fR
  453. (see the example below in the description of the
  454. \fB\-\-left\-right\fR
  455. option)\&. However, it shows the commits that were cherry\-picked from the other branch (for example,
  456. \(lq3rd on b\(rq
  457. may be cherry\-picked from branch A)\&. With this option, such pairs of commits are excluded from the output\&.
  458. .RE
  459. .PP
  460. \-\-left\-only, \-\-right\-only
  461. .RS 4
  462. List only commits on the respective side of a symmetric difference, i\&.e\&. only those which would be marked < resp\&. > by
  463. \fB\-\-left\-right\fR\&.
  464. .sp
  465. For example,
  466. \fB\-\-cherry\-pick\fR
  467. \fB\-\-right\-only\fR
  468. \fBA\fR\fB\&.\&.\&.\fR\fBB\fR
  469. omits those commits from
  470. \fBB\fR
  471. which are in
  472. \fBA\fR
  473. or are patch\-equivalent to a commit in
  474. \fBA\fR\&. In other words, this lists the
  475. \fB+\fR
  476. commits from
  477. \fBgit\fR
  478. \fBcherry\fR
  479. \fBA\fR
  480. \fBB\fR\&. More precisely,
  481. \fB\-\-cherry\-pick\fR
  482. \fB\-\-right\-only\fR
  483. \fB\-\-no\-merges\fR
  484. gives the exact list\&.
  485. .RE
  486. .PP
  487. \-\-cherry
  488. .RS 4
  489. A synonym for
  490. \fB\-\-right\-only\fR
  491. \fB\-\-cherry\-mark\fR
  492. \fB\-\-no\-merges\fR; useful to limit the output to the commits on our side and mark those that have been applied to the other side of a forked history with
  493. \fBgit\fR
  494. \fBlog\fR
  495. \fB\-\-cherry\fR
  496. \fBupstream\fR\fB\&.\&.\&.\fR\fBmybranch\fR, similar to
  497. \fBgit\fR
  498. \fBcherry\fR
  499. \fBupstream\fR
  500. \fBmybranch\fR\&.
  501. .RE
  502. .PP
  503. \-g, \-\-walk\-reflogs
  504. .RS 4
  505. Instead of walking the commit ancestry chain, walk reflog entries from the most recent one to older ones\&. When this option is used you cannot specify commits to exclude (that is,
  506. \fI^commit\fR,
  507. \fIcommit1\&.\&.commit2\fR, and
  508. \fIcommit1\&.\&.\&.commit2\fR
  509. notations cannot be used)\&.
  510. .sp
  511. With
  512. \fB\-\-pretty\fR
  513. format other than
  514. \fBoneline\fR
  515. and
  516. \fBreference\fR
  517. (for obvious reasons), this causes the output to have two extra lines of information taken from the reflog\&. The reflog designator in the output may be shown as
  518. \fBref@\fR{\fI<Nth>\fR} (where
  519. \fI<Nth>\fR
  520. is the reverse\-chronological index in the reflog) or as
  521. \fBref@\fR{\fI<timestamp>\fR} (with the
  522. \fI<timestamp>\fR
  523. for that entry), depending on a few rules:
  524. .sp
  525. .RS 4
  526. .ie n \{\
  527. \h'-04' 1.\h'+01'\c
  528. .\}
  529. .el \{\
  530. .sp -1
  531. .IP "  1." 4.2
  532. .\}
  533. If the starting point is specified as
  534. \fBref@\fR{\fI<Nth>\fR}, show the index format\&.
  535. .RE
  536. .sp
  537. .RS 4
  538. .ie n \{\
  539. \h'-04' 2.\h'+01'\c
  540. .\}
  541. .el \{\
  542. .sp -1
  543. .IP "  2." 4.2
  544. .\}
  545. If the starting point was specified as
  546. \fBref@\fR{now}, show the timestamp format\&.
  547. .RE
  548. .sp
  549. .RS 4
  550. .ie n \{\
  551. \h'-04' 3.\h'+01'\c
  552. .\}
  553. .el \{\
  554. .sp -1
  555. .IP "  3." 4.2
  556. .\}
  557. If neither was used, but
  558. \fB\-\-date\fR
  559. was given on the command line, show the timestamp in the format requested by
  560. \fB\-\-date\fR\&.
  561. .RE
  562. .sp
  563. .RS 4
  564. .ie n \{\
  565. \h'-04' 4.\h'+01'\c
  566. .\}
  567. .el \{\
  568. .sp -1
  569. .IP "  4." 4.2
  570. .\}
  571. Otherwise, show the index format\&.
  572. .RE
  573. .sp
  574. Under
  575. \fB\-\-pretty=oneline\fR, the commit message is prefixed with this information on the same line\&. This option cannot be combined with
  576. \fB\-\-reverse\fR\&. See also
  577. \fBgit-reflog\fR(1)\&.
  578. .sp
  579. Under
  580. \fB\-\-pretty=reference\fR, this information will not be shown at all\&.
  581. .RE
  582. .PP
  583. \-\-merge
  584. .RS 4
  585. Show commits touching conflicted paths in the range
  586. \fBHEAD\fR\fB\&.\&.\&.\fR\fI<other>\fR, where
  587. \fI<other>\fR
  588. is the first existing pseudoref in
  589. \fBMERGE_HEAD\fR,
  590. \fBCHERRY_PICK_HEAD\fR,
  591. \fBREVERT_HEAD\fR
  592. or
  593. \fBREBASE_HEAD\fR\&. Only works when the index has unmerged entries\&. This option can be used to show relevant commits when resolving conflicts from a 3\-way merge\&.
  594. .RE
  595. .PP
  596. \-\-boundary
  597. .RS 4
  598. Output excluded boundary commits\&. Boundary commits are prefixed with
  599. \fB\-\fR\&.
  600. .RE
  601. .PP
  602. \-\-use\-bitmap\-index
  603. .RS 4
  604. Try to speed up the traversal using the pack bitmap index (if one is available)\&. Note that when traversing with
  605. \fB\-\-objects\fR, trees and blobs will not have their associated path printed\&.
  606. .RE
  607. .PP
  608. \-\-progress=<header>
  609. .RS 4
  610. Show progress reports on stderr as objects are considered\&. The
  611. \fI<header>\fR
  612. text will be printed with each progress update\&.
  613. .RE
  614. .SS "History Simplification"
  615. .sp
  616. Sometimes you are only interested in parts of the history, for example the commits modifying a particular <path>\&. But there are two parts of \fIHistory Simplification\fR, one part is selecting the commits and the other is how to do it, as there are various strategies to simplify the history\&.
  617. .sp
  618. The following options select the commits to be shown:
  619. .PP
  620. <paths>
  621. .RS 4
  622. Commits modifying the given <paths> are selected\&.
  623. .RE
  624. .PP
  625. \-\-simplify\-by\-decoration
  626. .RS 4
  627. Commits that are referred by some branch or tag are selected\&.
  628. .RE
  629. .sp
  630. Note that extra commits can be shown to give a meaningful history\&.
  631. .sp
  632. The following options affect the way the simplification is performed:
  633. .PP
  634. Default mode
  635. .RS 4
  636. Simplifies the history to the simplest history explaining the final state of the tree\&. Simplest because it prunes some side branches if the end result is the same (i\&.e\&. merging branches with the same content)
  637. .RE
  638. .PP
  639. \-\-show\-pulls
  640. .RS 4
  641. Include all commits from the default mode, but also any merge commits that are not TREESAME to the first parent but are TREESAME to a later parent\&. This mode is helpful for showing the merge commits that "first introduced" a change to a branch\&.
  642. .RE
  643. .PP
  644. \-\-full\-history
  645. .RS 4
  646. Same as the default mode, but does not prune some history\&.
  647. .RE
  648. .PP
  649. \-\-dense
  650. .RS 4
  651. Only the selected commits are shown, plus some to have a meaningful history\&.
  652. .RE
  653. .PP
  654. \-\-sparse
  655. .RS 4
  656. All commits in the simplified history are shown\&.
  657. .RE
  658. .PP
  659. \-\-simplify\-merges
  660. .RS 4
  661. Additional option to
  662. \fB\-\-full\-history\fR
  663. to remove some needless merges from the resulting history, as there are no selected commits contributing to this merge\&.
  664. .RE
  665. .PP
  666. \-\-ancestry\-path[=<commit>]
  667. .RS 4
  668. When given a range of commits to display (e\&.g\&.
  669. \fIcommit1\&.\&.commit2\fR
  670. or
  671. \fIcommit2 ^commit1\fR), and a commit <commit> in that range, only display commits in that range that are ancestors of <commit>, descendants of <commit>, or <commit> itself\&. If no commit is specified, use
  672. \fIcommit1\fR
  673. (the excluded part of the range) as <commit>\&. Can be passed multiple times; if so, a commit is included if it is any of the commits given or if it is an ancestor or descendant of one of them\&.
  674. .RE
  675. .sp
  676. A more detailed explanation follows\&.
  677. .sp
  678. Suppose you specified \fBfoo\fR as the <paths>\&. We shall call commits that modify \fBfoo\fR !TREESAME, and the rest TREESAME\&. (In a diff filtered for \fBfoo\fR, they look different and equal, respectively\&.)
  679. .sp
  680. In the following, we will always refer to the same example history to illustrate the differences between simplification settings\&. We assume that you are filtering for a file \fBfoo\fR in this commit graph:
  681. .sp
  682. .if n \{\
  683. .RS 4
  684. .\}
  685. .nf
  686.           \&.\-A\-\-\-M\-\-\-N\-\-\-O\-\-\-P\-\-\-Q
  687.          /     /   /   /   /   /
  688.         I     B   C   D   E   Y
  689.          \e   /   /   /   /   /
  690.           `\-\-\-\-\-\-\-\-\-\-\-\-\-\*(Aq   X
  691. .fi
  692. .if n \{\
  693. .RE
  694. .\}
  695. .sp
  696. The horizontal line of history A\-\-\-Q is taken to be the first parent of each merge\&. The commits are:
  697. .sp
  698. .RS 4
  699. .ie n \{\
  700. \h'-04'\(bu\h'+03'\c
  701. .\}
  702. .el \{\
  703. .sp -1
  704. .IP \(bu 2.3
  705. .\}
  706. \fBI\fR
  707. is the initial commit, in which
  708. \fBfoo\fR
  709. exists with contents
  710. \(lqasdf\(rq, and a file
  711. \fBquux\fR
  712. exists with contents
  713. \(lqquux\(rq\&. Initial commits are compared to an empty tree, so
  714. \fBI\fR
  715. is !TREESAME\&.
  716. .RE
  717. .sp
  718. .RS 4
  719. .ie n \{\
  720. \h'-04'\(bu\h'+03'\c
  721. .\}
  722. .el \{\
  723. .sp -1
  724. .IP \(bu 2.3
  725. .\}
  726. In
  727. \fBA\fR,
  728. \fBfoo\fR
  729. contains just
  730. \(lqfoo\(rq\&.
  731. .RE
  732. .sp
  733. .RS 4
  734. .ie n \{\
  735. \h'-04'\(bu\h'+03'\c
  736. .\}
  737. .el \{\
  738. .sp -1
  739. .IP \(bu 2.3
  740. .\}
  741. \fBB\fR
  742. contains the same change as
  743. \fBA\fR\&. Its merge
  744. \fBM\fR
  745. is trivial and hence TREESAME to all parents\&.
  746. .RE
  747. .sp
  748. .RS 4
  749. .ie n \{\
  750. \h'-04'\(bu\h'+03'\c
  751. .\}
  752. .el \{\
  753. .sp -1
  754. .IP \(bu 2.3
  755. .\}
  756. \fBC\fR
  757. does not change
  758. \fBfoo\fR, but its merge
  759. \fBN\fR
  760. changes it to
  761. \(lqfoobar\(rq, so it is not TREESAME to any parent\&.
  762. .RE
  763. .sp
  764. .RS 4
  765. .ie n \{\
  766. \h'-04'\(bu\h'+03'\c
  767. .\}
  768. .el \{\
  769. .sp -1
  770. .IP \(bu 2.3
  771. .\}
  772. \fBD\fR
  773. sets
  774. \fBfoo\fR
  775. to
  776. \(lqbaz\(rq\&. Its merge
  777. \fBO\fR
  778. combines the strings from
  779. \fBN\fR
  780. and
  781. \fBD\fR
  782. to
  783. \(lqfoobarbaz\(rq; i\&.e\&., it is not TREESAME to any parent\&.
  784. .RE
  785. .sp
  786. .RS 4
  787. .ie n \{\
  788. \h'-04'\(bu\h'+03'\c
  789. .\}
  790. .el \{\
  791. .sp -1
  792. .IP \(bu 2.3
  793. .\}
  794. \fBE\fR
  795. changes
  796. \fBquux\fR
  797. to
  798. \(lqxyzzy\(rq, and its merge
  799. \fBP\fR
  800. combines the strings to
  801. \(lqquux xyzzy\(rq\&.
  802. \fBP\fR
  803. is TREESAME to
  804. \fBO\fR, but not to
  805. \fBE\fR\&.
  806. .RE
  807. .sp
  808. .RS 4
  809. .ie n \{\
  810. \h'-04'\(bu\h'+03'\c
  811. .\}
  812. .el \{\
  813. .sp -1
  814. .IP \(bu 2.3
  815. .\}
  816. \fBX\fR
  817. is an independent root commit that added a new file
  818. \fBside\fR, and
  819. \fBY\fR
  820. modified it\&.
  821. \fBY\fR
  822. is TREESAME to
  823. \fBX\fR\&. Its merge
  824. \fBQ\fR
  825. added
  826. \fBside\fR
  827. to
  828. \fBP\fR, and
  829. \fBQ\fR
  830. is TREESAME to
  831. \fBP\fR, but not to
  832. \fBY\fR\&.
  833. .RE
  834. .sp
  835. \fBrev\-list\fR walks backwards through history, including or excluding commits based on whether \fB\-\-full\-history\fR and/or parent rewriting (via \fB\-\-parents\fR or \fB\-\-children\fR) are used\&. The following settings are available\&.
  836. .PP
  837. Default mode
  838. .RS 4
  839. Commits are included if they are not TREESAME to any parent (though this can be changed, see
  840. \fB\-\-sparse\fR
  841. below)\&. If the commit was a merge, and it was TREESAME to one parent, follow only that parent\&. (Even if there are several TREESAME parents, follow only one of them\&.) Otherwise, follow all parents\&.
  842. .sp
  843. This results in:
  844. .sp
  845. .if n \{\
  846. .RS 4
  847. .\}
  848. .nf
  849.           \&.\-A\-\-\-N\-\-\-O
  850.          /     /   /
  851.         I\-\-\-\-\-\-\-\-\-D
  852. .fi
  853. .if n \{\
  854. .RE
  855. .\}
  856. .sp
  857. Note how the rule to only follow the TREESAME parent, if one is available, removed
  858. \fBB\fR
  859. from consideration entirely\&.
  860. \fBC\fR
  861. was considered via
  862. \fBN\fR, but is TREESAME\&. Root commits are compared to an empty tree, so
  863. \fBI\fR
  864. is !TREESAME\&.
  865. .sp
  866. Parent/child relations are only visible with
  867. \fB\-\-parents\fR, but that does not affect the commits selected in default mode, so we have shown the parent lines\&.
  868. .RE
  869. .PP
  870. \-\-full\-history without parent rewriting
  871. .RS 4
  872. This mode differs from the default in one point: always follow all parents of a merge, even if it is TREESAME to one of them\&. Even if more than one side of the merge has commits that are included, this does not imply that the merge itself is! In the example, we get
  873. .sp
  874. .if n \{\
  875. .RS 4
  876. .\}
  877. .nf
  878.         I  A  B  N  D  O  P  Q
  879. .fi
  880. .if n \{\
  881. .RE
  882. .\}
  883. .sp
  884. \fBM\fR
  885. was excluded because it is TREESAME to both parents\&.
  886. \fBE\fR,
  887. \fBC\fR
  888. and
  889. \fBB\fR
  890. were all walked, but only
  891. \fBB\fR
  892. was !TREESAME, so the others do not appear\&.
  893. .sp
  894. Note that without parent rewriting, it is not really possible to talk about the parent/child relationships between the commits, so we show them disconnected\&.
  895. .RE
  896. .PP
  897. \-\-full\-history with parent rewriting
  898. .RS 4
  899. Ordinary commits are only included if they are !TREESAME (though this can be changed, see
  900. \fB\-\-sparse\fR
  901. below)\&.
  902. .sp
  903. Merges are always included\&. However, their parent list is rewritten: Along each parent, prune away commits that are not included themselves\&. This results in
  904. .sp
  905. .if n \{\
  906. .RS 4
  907. .\}
  908. .nf
  909.           \&.\-A\-\-\-M\-\-\-N\-\-\-O\-\-\-P\-\-\-Q
  910.          /     /   /   /   /
  911.         I     B   /   D   /
  912.          \e   /   /   /   /
  913.           `\-\-\-\-\-\-\-\-\-\-\-\-\-\*(Aq
  914. .fi
  915. .if n \{\
  916. .RE
  917. .\}
  918. .sp
  919. Compare to
  920. \fB\-\-full\-history\fR
  921. without rewriting above\&. Note that
  922. \fBE\fR
  923. was pruned away because it is TREESAME, but the parent list of P was rewritten to contain
  924. \fBE\fR\*(Aqs parent
  925. \fBI\fR\&. The same happened for
  926. \fBC\fR
  927. and
  928. \fBN\fR, and
  929. \fBX\fR,
  930. \fBY\fR
  931. and
  932. \fBQ\fR\&.
  933. .RE
  934. .sp
  935. In addition to the above settings, you can change whether TREESAME affects inclusion:
  936. .PP
  937. \-\-dense
  938. .RS 4
  939. Commits that are walked are included if they are not TREESAME to any parent\&.
  940. .RE
  941. .PP
  942. \-\-sparse
  943. .RS 4
  944. All commits that are walked are included\&.
  945. .sp
  946. Note that without
  947. \fB\-\-full\-history\fR, this still simplifies merges: if one of the parents is TREESAME, we follow only that one, so the other sides of the merge are never walked\&.
  948. .RE
  949. .PP
  950. \-\-simplify\-merges
  951. .RS 4
  952. First, build a history graph in the same way that
  953. \fB\-\-full\-history\fR
  954. with parent rewriting does (see above)\&.
  955. .sp
  956. Then simplify each commit
  957. \fBC\fR
  958. to its replacement
  959. \fBC\fR\*(Aq in the final history according to the following rules:
  960. .sp
  961. .RS 4
  962. .ie n \{\
  963. \h'-04'\(bu\h'+03'\c
  964. .\}
  965. .el \{\
  966. .sp -1
  967. .IP \(bu 2.3
  968. .\}
  969. Set
  970. \fBC\fR\*(Aq to
  971. \fBC\fR\&.
  972. .RE
  973. .sp
  974. .RS 4
  975. .ie n \{\
  976. \h'-04'\(bu\h'+03'\c
  977. .\}
  978. .el \{\
  979. .sp -1
  980. .IP \(bu 2.3
  981. .\}
  982. Replace each parent
  983. \fBP\fR
  984. of
  985. \fBC\fR\*(Aq with its simplification
  986. \fBP\fR\*(Aq\&. In the process, drop parents that are ancestors of other parents or that are root commits TREESAME to an empty tree, and remove duplicates, but take care to never drop all parents that we are TREESAME to\&.
  987. .RE
  988. .sp
  989. .RS 4
  990. .ie n \{\
  991. \h'-04'\(bu\h'+03'\c
  992. .\}
  993. .el \{\
  994. .sp -1
  995. .IP \(bu 2.3
  996. .\}
  997. If after this parent rewriting,
  998. \fBC\fR\*(Aq is a root or merge commit (has zero or >1 parents), a boundary commit, or !TREESAME, it remains\&. Otherwise, it is replaced with its only parent\&.
  999. .RE
  1000. .sp
  1001. The effect of this is best shown by way of comparing to
  1002. \fB\-\-full\-history\fR
  1003. with parent rewriting\&. The example turns into:
  1004. .sp
  1005. .if n \{\
  1006. .RS 4
  1007. .\}
  1008. .nf
  1009.           \&.\-A\-\-\-M\-\-\-N\-\-\-O
  1010.          /     /       /
  1011.         I     B       D
  1012.          \e   /       /
  1013.           `\-\-\-\-\-\-\-\-\-\*(Aq
  1014. .fi
  1015. .if n \{\
  1016. .RE
  1017. .\}
  1018. .sp
  1019. Note the major differences in
  1020. \fBN\fR,
  1021. \fBP\fR, and
  1022. \fBQ\fR
  1023. over
  1024. \fB\-\-full\-history\fR:
  1025. .sp
  1026. .RS 4
  1027. .ie n \{\
  1028. \h'-04'\(bu\h'+03'\c
  1029. .\}
  1030. .el \{\
  1031. .sp -1
  1032. .IP \(bu 2.3
  1033. .\}
  1034. \fBN\fR\*(Aqs parent list had
  1035. \fBI\fR
  1036. removed, because it is an ancestor of the other parent
  1037. \fBM\fR\&. Still,
  1038. \fBN\fR
  1039. remained because it is !TREESAME\&.
  1040. .RE
  1041. .sp
  1042. .RS 4
  1043. .ie n \{\
  1044. \h'-04'\(bu\h'+03'\c
  1045. .\}
  1046. .el \{\
  1047. .sp -1
  1048. .IP \(bu 2.3
  1049. .\}
  1050. \fBP\fR\*(Aqs parent list similarly had
  1051. \fBI\fR
  1052. removed\&.
  1053. \fBP\fR
  1054. was then removed completely, because it had one parent and is TREESAME\&.
  1055. .RE
  1056. .sp
  1057. .RS 4
  1058. .ie n \{\
  1059. \h'-04'\(bu\h'+03'\c
  1060. .\}
  1061. .el \{\
  1062. .sp -1
  1063. .IP \(bu 2.3
  1064. .\}
  1065. \fBQ\fR\*(Aqs parent list had
  1066. \fBY\fR
  1067. simplified to
  1068. \fBX\fR\&.
  1069. \fBX\fR
  1070. was then removed, because it was a TREESAME root\&.
  1071. \fBQ\fR
  1072. was then removed completely, because it had one parent and is TREESAME\&.
  1073. .RE
  1074. .RE
  1075. .sp
  1076. There is another simplification mode available:
  1077. .PP
  1078. \-\-ancestry\-path[=<commit>]
  1079. .RS 4
  1080. Limit the displayed commits to those which are an ancestor of <commit>, or which are a descendant of <commit>, or are <commit> itself\&.
  1081. .sp
  1082. As an example use case, consider the following commit history:
  1083. .sp
  1084. .if n \{\
  1085. .RS 4
  1086. .\}
  1087. .nf
  1088.             D\-\-\-E\-\-\-\-\-\-\-F
  1089.            /     \e       \e
  1090.           B\-\-\-C\-\-\-G\-\-\-H\-\-\-I\-\-\-J
  1091.          /                     \e
  1092.         A\-\-\-\-\-\-\-K\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-L\-\-M
  1093. .fi
  1094. .if n \{\
  1095. .RE
  1096. .\}
  1097. .sp
  1098. A regular
  1099. \fID\&.\&.M\fR
  1100. computes the set of commits that are ancestors of
  1101. \fBM\fR, but excludes the ones that are ancestors of
  1102. \fBD\fR\&. This is useful to see what happened to the history leading to
  1103. \fBM\fR
  1104. since
  1105. \fBD\fR, in the sense that
  1106. \(lqwhat does \fBM\fR have that did not exist in \fBD\fR\(rq\&. The result in this example would be all the commits, except
  1107. \fBA\fR
  1108. and
  1109. \fBB\fR
  1110. (and
  1111. \fBD\fR
  1112. itself, of course)\&.
  1113. .sp
  1114. When we want to find out what commits in
  1115. \fBM\fR
  1116. are contaminated with the bug introduced by
  1117. \fBD\fR
  1118. and need fixing, however, we might want to view only the subset of
  1119. \fID\&.\&.M\fR
  1120. that are actually descendants of
  1121. \fBD\fR, i\&.e\&. excluding
  1122. \fBC\fR
  1123. and
  1124. \fBK\fR\&. This is exactly what the
  1125. \fB\-\-ancestry\-path\fR
  1126. option does\&. Applied to the
  1127. \fID\&.\&.M\fR
  1128. range, it results in:
  1129. .sp
  1130. .if n \{\
  1131. .RS 4
  1132. .\}
  1133. .nf
  1134.                 E\-\-\-\-\-\-\-F
  1135.                  \e       \e
  1136.                   G\-\-\-H\-\-\-I\-\-\-J
  1137.                                \e
  1138.                                 L\-\-M
  1139. .fi
  1140. .if n \{\
  1141. .RE
  1142. .\}
  1143. .sp
  1144. We can also use
  1145. \fB\-\-ancestry\-path=D\fR
  1146. instead of
  1147. \fB\-\-ancestry\-path\fR
  1148. which means the same thing when applied to the
  1149. \fID\&.\&.M\fR
  1150. range but is just more explicit\&.
  1151. .sp
  1152. If we instead are interested in a given topic within this range, and all commits affected by that topic, we may only want to view the subset of
  1153. \fBD\fR\fB\&.\&.\fR\fBM\fR
  1154. which contain that topic in their ancestry path\&. So, using
  1155. \fB\-\-ancestry\-path=H\fR
  1156. \fBD\fR\fB\&.\&.\fR\fBM\fR
  1157. for example would result in:
  1158. .sp
  1159. .if n \{\
  1160. .RS 4
  1161. .\}
  1162. .nf
  1163.                 E
  1164.                  \e
  1165.                   G\-\-\-H\-\-\-I\-\-\-J
  1166.                                \e
  1167.                                 L\-\-M
  1168. .fi
  1169. .if n \{\
  1170. .RE
  1171. .\}
  1172. .sp
  1173. Whereas
  1174. \fB\-\-ancestry\-path=K\fR
  1175. \fBD\fR\fB\&.\&.\fR\fBM\fR
  1176. would result in
  1177. .sp
  1178. .if n \{\
  1179. .RS 4
  1180. .\}
  1181. .nf
  1182.                 K\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-L\-\-M
  1183. .fi
  1184. .if n \{\
  1185. .RE
  1186. .\}
  1187. .RE
  1188. .sp
  1189. Before discussing another option, \fB\-\-show\-pulls\fR, we need to create a new example history\&.
  1190. .sp
  1191. A common problem users face when looking at simplified history is that a commit they know changed a file somehow does not appear in the file\(cqs simplified history\&. Let\(cqs demonstrate a new example and show how options such as \fB\-\-full\-history\fR and \fB\-\-simplify\-merges\fR works in that case:
  1192. .sp
  1193. .if n \{\
  1194. .RS 4
  1195. .\}
  1196. .nf
  1197.           \&.\-A\-\-\-M\-\-\-\-\-C\-\-N\-\-\-O\-\-\-P
  1198.          /     / \e  \e  \e/   /   /
  1199.         I     B   \e  R\-\*(Aq`\-Z\*(Aq   /
  1200.          \e   /     \e/         /
  1201.           \e /      /\e        /
  1202.            `\-\-\-X\-\-\*(Aq  `\-\-\-Y\-\-\*(Aq
  1203. .fi
  1204. .if n \{\
  1205. .RE
  1206. .\}
  1207. .sp
  1208. For this example, suppose \fBI\fR created \fBfile\&.txt\fR which was modified by \fBA\fR, \fBB\fR, and \fBX\fR in different ways\&. The single\-parent commits \fBC\fR, \fBZ\fR, and \fBY\fR do not change \fBfile\&.txt\fR\&. The merge commit \fBM\fR was created by resolving the merge conflict to include both changes from \fBA\fR and \fBB\fR and hence is not TREESAME to either\&. The merge commit \fBR\fR, however, was created by ignoring the contents of \fBfile\&.txt\fR at \fBM\fR and taking only the contents of \fBfile\&.txt\fR at \fBX\fR\&. Hence, \fBR\fR is TREESAME to \fBX\fR but not \fBM\fR\&. Finally, the natural merge resolution to create \fBN\fR is to take the contents of \fBfile\&.txt\fR at \fBR\fR, so \fBN\fR is TREESAME to \fBR\fR but not \fBC\fR\&. The merge commits \fBO\fR and \fBP\fR are TREESAME to their first parents, but not to their second parents, \fBZ\fR and \fBY\fR respectively\&.
  1209. .sp
  1210. When using the default mode, \fBN\fR and \fBR\fR both have a TREESAME parent, so those edges are walked and the others are ignored\&. The resulting history graph is:
  1211. .sp
  1212. .if n \{\
  1213. .RS 4
  1214. .\}
  1215. .nf
  1216.         I\-\-\-X
  1217. .fi
  1218. .if n \{\
  1219. .RE
  1220. .\}
  1221. .sp
  1222. When using \fB\-\-full\-history\fR, Git walks every edge\&. This will discover the commits \fBA\fR and \fBB\fR and the merge \fBM\fR, but also will reveal the merge commits \fBO\fR and \fBP\fR\&. With parent rewriting, the resulting graph is:
  1223. .sp
  1224. .if n \{\
  1225. .RS 4
  1226. .\}
  1227. .nf
  1228.           \&.\-A\-\-\-M\-\-\-\-\-\-\-\-N\-\-\-O\-\-\-P
  1229.          /     / \e  \e  \e/   /   /
  1230.         I     B   \e  R\-\*(Aq`\-\-\*(Aq   /
  1231.          \e   /     \e/         /
  1232.           \e /      /\e        /
  1233.            `\-\-\-X\-\-\*(Aq  `\-\-\-\-\-\-\*(Aq
  1234. .fi
  1235. .if n \{\
  1236. .RE
  1237. .\}
  1238. .sp
  1239. Here, the merge commits \fBO\fR and \fBP\fR contribute extra noise, as they did not actually contribute a change to \fBfile\&.txt\fR\&. They only merged a topic that was based on an older version of \fBfile\&.txt\fR\&. This is a common issue in repositories using a workflow where many contributors work in parallel and merge their topic branches along a single trunk: many unrelated merges appear in the \fB\-\-full\-history\fR results\&.
  1240. .sp
  1241. When using the \fB\-\-simplify\-merges\fR option, the commits \fBO\fR and \fBP\fR disappear from the results\&. This is because the rewritten second parents of \fBO\fR and \fBP\fR are reachable from their first parents\&. Those edges are removed and then the commits look like single\-parent commits that are TREESAME to their parent\&. This also happens to the commit \fBN\fR, resulting in a history view as follows:
  1242. .sp
  1243. .if n \{\
  1244. .RS 4
  1245. .\}
  1246. .nf
  1247.           \&.\-A\-\-\-M\-\-\&.
  1248.          /     /    \e
  1249.         I     B      R
  1250.          \e   /      /
  1251.           \e /      /
  1252.            `\-\-\-X\-\-\*(Aq
  1253. .fi
  1254. .if n \{\
  1255. .RE
  1256. .\}
  1257. .sp
  1258. In this view, we see all of the important single\-parent changes from \fBA\fR, \fBB\fR, and \fBX\fR\&. We also see the carefully\-resolved merge \fBM\fR and the not\-so\-carefully\-resolved merge \fBR\fR\&. This is usually enough information to determine why the commits \fBA\fR and \fBB\fR "disappeared" from history in the default view\&. However, there are a few issues with this approach\&.
  1259. .sp
  1260. The first issue is performance\&. Unlike any previous option, the \fB\-\-simplify\-merges\fR option requires walking the entire commit history before returning a single result\&. This can make the option difficult to use for very large repositories\&.
  1261. .sp
  1262. The second issue is one of auditing\&. When many contributors are working on the same repository, it is important which merge commits introduced a change into an important branch\&. The problematic merge \fBR\fR above is not likely to be the merge commit that was used to merge into an important branch\&. Instead, the merge \fBN\fR was used to merge \fBR\fR and \fBX\fR into the important branch\&. This commit may have information about why the change \fBX\fR came to override the changes from \fBA\fR and \fBB\fR in its commit message\&.
  1263. .PP
  1264. \-\-show\-pulls
  1265. .RS 4
  1266. In addition to the commits shown in the default history, show each merge commit that is not TREESAME to its first parent but is TREESAME to a later parent\&.
  1267. .sp
  1268. When a merge commit is included by
  1269. \fB\-\-show\-pulls\fR, the merge is treated as if it "pulled" the change from another branch\&. When using
  1270. \fB\-\-show\-pulls\fR
  1271. on this example (and no other options) the resulting graph is:
  1272. .sp
  1273. .if n \{\
  1274. .RS 4
  1275. .\}
  1276. .nf
  1277.         I\-\-\-X\-\-\-R\-\-\-N
  1278. .fi
  1279. .if n \{\
  1280. .RE
  1281. .\}
  1282. .sp
  1283. Here, the merge commits
  1284. \fBR\fR
  1285. and
  1286. \fBN\fR
  1287. are included because they pulled the commits
  1288. \fBX\fR
  1289. and
  1290. \fBR\fR
  1291. into the base branch, respectively\&. These merges are the reason the commits
  1292. \fBA\fR
  1293. and
  1294. \fBB\fR
  1295. do not appear in the default history\&.
  1296. .sp
  1297. When
  1298. \fB\-\-show\-pulls\fR
  1299. is paired with
  1300. \fB\-\-simplify\-merges\fR, the graph includes all of the necessary information:
  1301. .sp
  1302. .if n \{\
  1303. .RS 4
  1304. .\}
  1305. .nf
  1306.           \&.\-A\-\-\-M\-\-\&.   N
  1307.          /     /    \e /
  1308.         I     B      R
  1309.          \e   /      /
  1310.           \e /      /
  1311.            `\-\-\-X\-\-\*(Aq
  1312. .fi
  1313. .if n \{\
  1314. .RE
  1315. .\}
  1316. .sp
  1317. Notice that since
  1318. \fBM\fR
  1319. is reachable from
  1320. \fBR\fR, the edge from
  1321. \fBN\fR
  1322. to
  1323. \fBM\fR
  1324. was simplified away\&. However,
  1325. \fBN\fR
  1326. still appears in the history as an important commit because it "pulled" the change
  1327. \fBR\fR
  1328. into the main branch\&.
  1329. .RE
  1330. .sp
  1331. The \fB\-\-simplify\-by\-decoration\fR option allows you to view only the big picture of the topology of the history, by omitting commits that are not referenced by tags\&. Commits are marked as !TREESAME (in other words, kept after history simplification rules described above) if (1) they are referenced by tags, or (2) they change the contents of the paths given on the command line\&. All other commits are marked as TREESAME (subject to be simplified away)\&.
  1332. .SS "Bisection Helpers"
  1333. .PP
  1334. \-\-bisect
  1335. .RS 4
  1336. Limit output to the one commit object which is roughly halfway between included and excluded commits\&. Note that the bad bisection ref
  1337. \fBrefs/bisect/bad\fR
  1338. is added to the included commits (if it exists) and the good bisection refs
  1339. \fBrefs/bisect/good\-\fR* are added to the excluded commits (if they exist)\&. Thus, supposing there are no refs in
  1340. \fBrefs/bisect/\fR, if
  1341. .sp
  1342. .if n \{\
  1343. .RS 4
  1344. .\}
  1345. .nf
  1346.         $ git rev\-list \-\-bisect foo ^bar ^baz
  1347. .fi
  1348. .if n \{\
  1349. .RE
  1350. .\}
  1351. .sp
  1352. outputs
  1353. \fImidpoint\fR, the output of the two commands
  1354. .sp
  1355. .if n \{\
  1356. .RS 4
  1357. .\}
  1358. .nf
  1359.         $ git rev\-list foo ^midpoint
  1360.         $ git rev\-list midpoint ^bar ^baz
  1361. .fi
  1362. .if n \{\
  1363. .RE
  1364. .\}
  1365. .sp
  1366. would be of roughly the same length\&. Finding the change which introduces a regression is thus reduced to a binary search: repeatedly generate and test new \*(Aqmidpoint\(cqs until the commit chain is of length one\&.
  1367. .RE
  1368. .PP
  1369. \-\-bisect\-vars
  1370. .RS 4
  1371. This calculates the same as
  1372. \fB\-\-bisect\fR, except that refs in
  1373. \fBrefs/bisect/\fR
  1374. are not used, and except that this outputs text ready to be eval\(cqed by the shell\&. These lines will assign the name of the midpoint revision to the variable
  1375. \fBbisect_rev\fR, and the expected number of commits to be tested after
  1376. \fBbisect_rev\fR
  1377. is tested to
  1378. \fBbisect_nr\fR, the expected number of commits to be tested if
  1379. \fBbisect_rev\fR
  1380. turns out to be good to
  1381. \fBbisect_good\fR, the expected number of commits to be tested if
  1382. \fBbisect_rev\fR
  1383. turns out to be bad to
  1384. \fBbisect_bad\fR, and the number of commits we are bisecting right now to
  1385. \fBbisect_all\fR\&.
  1386. .RE
  1387. .PP
  1388. \-\-bisect\-all
  1389. .RS 4
  1390. This outputs all the commit objects between the included and excluded commits, ordered by their distance to the included and excluded commits\&. Refs in
  1391. \fBrefs/bisect/\fR
  1392. are not used\&. The farthest from them is displayed first\&. (This is the only one displayed by
  1393. \fB\-\-bisect\fR\&.)
  1394. .sp
  1395. This is useful because it makes it easy to choose a good commit to test when you want to avoid to test some of them for some reason (they may not compile for example)\&.
  1396. .sp
  1397. This option can be used along with
  1398. \fB\-\-bisect\-vars\fR, in this case, after all the sorted commit objects, there will be the same text as if
  1399. \fB\-\-bisect\-vars\fR
  1400. had been used alone\&.
  1401. .RE
  1402. .SS "Commit Ordering"
  1403. .sp
  1404. By default, the commits are shown in reverse chronological order\&.
  1405. .PP
  1406. \-\-date\-order
  1407. .RS 4
  1408. Show no parents before all of its children are shown, but otherwise show commits in the commit timestamp order\&.
  1409. .RE
  1410. .PP
  1411. \-\-author\-date\-order
  1412. .RS 4
  1413. Show no parents before all of its children are shown, but otherwise show commits in the author timestamp order\&.
  1414. .RE
  1415. .PP
  1416. \-\-topo\-order
  1417. .RS 4
  1418. Show no parents before all of its children are shown, and avoid showing commits on multiple lines of history intermixed\&.
  1419. .sp
  1420. For example, in a commit history like this:
  1421. .sp
  1422. .if n \{\
  1423. .RS 4
  1424. .\}
  1425. .nf
  1426.     \-\-\-1\-\-\-\-2\-\-\-\-4\-\-\-\-7
  1427.         \e              \e
  1428.          3\-\-\-\-5\-\-\-\-6\-\-\-\-8\-\-\-
  1429. .fi
  1430. .if n \{\
  1431. .RE
  1432. .\}
  1433. .sp
  1434. where the numbers denote the order of commit timestamps,
  1435. \fBgit\fR
  1436. \fBrev\-list\fR
  1437. and friends with
  1438. \fB\-\-date\-order\fR
  1439. show the commits in the timestamp order: 8 7 6 5 4 3 2 1\&.
  1440. .sp
  1441. With
  1442. \fB\-\-topo\-order\fR, they would show 8 6 5 3 7 4 2 1 (or 8 7 4 2 6 5 3 1); some older commits are shown before newer ones in order to avoid showing the commits from two parallel development track mixed together\&.
  1443. .RE
  1444. .PP
  1445. \-\-reverse
  1446. .RS 4
  1447. Output the commits chosen to be shown (see Commit Limiting section above) in reverse order\&. Cannot be combined with
  1448. \fB\-\-walk\-reflogs\fR\&.
  1449. .RE
  1450. .SS "Object Traversal"
  1451. .sp
  1452. These options are mostly targeted for packing of Git repositories\&.
  1453. .PP
  1454. \-\-objects
  1455. .RS 4
  1456. Print the object IDs of any object referenced by the listed commits\&.
  1457. \fB\-\-objects\fR
  1458. \fBfoo\fR
  1459. \fB^bar\fR
  1460. thus means
  1461. \(lqsend me all object IDs which I need to download if I have the commit object \fIbar\fR but not \fIfoo\fR\(rq\&. See also
  1462. \fB\-\-object\-names\fR
  1463. below\&.
  1464. .RE
  1465. .PP
  1466. \-\-in\-commit\-order
  1467. .RS 4
  1468. Print tree and blob ids in order of the commits\&. The tree and blob ids are printed after they are first referenced by a commit\&.
  1469. .RE
  1470. .PP
  1471. \-\-objects\-edge
  1472. .RS 4
  1473. Similar to
  1474. \fB\-\-objects\fR, but also print the IDs of excluded commits prefixed with a
  1475. \(lq\-\(rq
  1476. character\&. This is used by
  1477. \fBgit-pack-objects\fR(1)
  1478. to build a
  1479. \(lqthin\(rq
  1480. pack, which records objects in deltified form based on objects contained in these excluded commits to reduce network traffic\&.
  1481. .RE
  1482. .PP
  1483. \-\-objects\-edge\-aggressive
  1484. .RS 4
  1485. Similar to
  1486. \fB\-\-objects\-edge\fR, but it tries harder to find excluded commits at the cost of increased time\&. This is used instead of
  1487. \fB\-\-objects\-edge\fR
  1488. to build
  1489. \(lqthin\(rq
  1490. packs for shallow repositories\&.
  1491. .RE
  1492. .PP
  1493. \-\-indexed\-objects
  1494. .RS 4
  1495. Pretend as if all trees and blobs used by the index are listed on the command line\&. Note that you probably want to use
  1496. \fB\-\-objects\fR, too\&.
  1497. .RE
  1498. .PP
  1499. \-\-unpacked
  1500. .RS 4
  1501. Only useful with
  1502. \fB\-\-objects\fR; print the object IDs that are not in packs\&.
  1503. .RE
  1504. .PP
  1505. \-\-object\-names
  1506. .RS 4
  1507. Only useful with
  1508. \fB\-\-objects\fR; print the names of the object IDs that are found\&. This is the default behavior\&. Note that the "name" of each object is ambiguous, and mostly intended as a hint for packing objects\&. In particular: no distinction is made between the names of tags, trees, and blobs; path names may be modified to remove newlines; and if an object would appear multiple times with different names, only one name is shown\&.
  1509. .RE
  1510. .PP
  1511. \-\-no\-object\-names
  1512. .RS 4
  1513. Only useful with
  1514. \fB\-\-objects\fR; does not print the names of the object IDs that are found\&. This inverts
  1515. \fB\-\-object\-names\fR\&. This flag allows the output to be more easily parsed by commands such as
  1516. \fBgit-cat-file\fR(1)\&.
  1517. .RE
  1518. .PP
  1519. \-\-filter=<filter\-spec>
  1520. .RS 4
  1521. Only useful with one of the
  1522. \fB\-\-objects\fR*; omits objects (usually blobs) from the list of printed objects\&. The
  1523. \fI<filter\-spec>\fR
  1524. may be one of the following:
  1525. .sp
  1526. The form
  1527. \fI\-\-filter=blob:none\fR
  1528. omits all blobs\&.
  1529. .sp
  1530. The form
  1531. \fI\-\-filter=blob:limit=<n>[kmg]\fR
  1532. omits blobs of size at least n bytes or units\&. n may be zero\&. The suffixes k, m, and g can be used to name units in KiB, MiB, or GiB\&. For example,
  1533. \fIblob:limit=1k\fR
  1534. is the same as
  1535. \fIblob:limit=1024\fR\&.
  1536. .sp
  1537. The form
  1538. \fI\-\-filter=object:type=(tag|commit|tree|blob)\fR
  1539. omits all objects which are not of the requested type\&.
  1540. .sp
  1541. The form
  1542. \fI\-\-filter=sparse:oid=<blob\-ish>\fR
  1543. uses a sparse\-checkout specification contained in the blob (or blob\-expression)
  1544. \fI<blob\-ish>\fR
  1545. to omit blobs that would not be required for a sparse checkout on the requested refs\&.
  1546. .sp
  1547. The form
  1548. \fI\-\-filter=tree:<depth>\fR
  1549. omits all blobs and trees whose depth from the root tree is >= <depth> (minimum depth if an object is located at multiple depths in the commits traversed)\&. <depth>=0 will not include any trees or blobs unless included explicitly in the command\-line (or standard input when \-\-stdin is used)\&. <depth>=1 will include only the tree and blobs which are referenced directly by a commit reachable from <commit> or an explicitly\-given object\&. <depth>=2 is like <depth>=1 while also including trees and blobs one more level removed from an explicitly\-given commit or tree\&.
  1550. .sp
  1551. Note that the form
  1552. \fI\-\-filter=sparse:path=<path>\fR
  1553. that wants to read from an arbitrary path on the filesystem has been dropped for security reasons\&.
  1554. .sp
  1555. Multiple
  1556. \fI\-\-filter=\fR
  1557. flags can be specified to combine filters\&. Only objects which are accepted by every filter are included\&.
  1558. .sp
  1559. The form
  1560. \fI\-\-filter=combine:<filter1>+<filter2>+\&...\:<filterN>\fR
  1561. can also be used to combined several filters, but this is harder than just repeating the
  1562. \fI\-\-filter\fR
  1563. flag and is usually not necessary\&. Filters are joined by
  1564. \fI+\fR
  1565. and individual filters are %\-encoded (i\&.e\&. URL\-encoded)\&. Besides the
  1566. \fI+\fR
  1567. and
  1568. \fI%\fR
  1569. characters, the following characters are reserved and also must be encoded:
  1570. \fB~\fR!@#$^&*()[]{}\e;",<>?\*(Aq` as well as all characters with ASCII code <=
  1571. \fB0x20\fR, which includes space and newline\&.
  1572. .sp
  1573. Other arbitrary characters can also be encoded\&. For instance,
  1574. \fIcombine:tree:3+blob:none\fR
  1575. and
  1576. \fIcombine:tree%3A3+blob%3Anone\fR
  1577. are equivalent\&.
  1578. .RE
  1579. .PP
  1580. \-\-no\-filter
  1581. .RS 4
  1582. Turn off any previous
  1583. \fB\-\-filter=\fR
  1584. argument\&.
  1585. .RE
  1586. .PP
  1587. \-\-filter\-provided\-objects
  1588. .RS 4
  1589. Filter the list of explicitly provided objects, which would otherwise always be printed even if they did not match any of the filters\&. Only useful with
  1590. \fB\-\-filter=\fR\&.
  1591. .RE
  1592. .PP
  1593. \-\-filter\-print\-omitted
  1594. .RS 4
  1595. Only useful with
  1596. \fB\-\-filter=\fR; prints a list of the objects omitted by the filter\&. Object IDs are prefixed with a
  1597. \(lq~\(rq
  1598. character\&.
  1599. .RE
  1600. .PP
  1601. \-\-missing=<missing\-action>
  1602. .RS 4
  1603. A debug option to help with future "partial clone" development\&. This option specifies how missing objects are handled\&.
  1604. .sp
  1605. The form
  1606. \fI\-\-missing=error\fR
  1607. requests that rev\-list stop with an error if a missing object is encountered\&. This is the default action\&.
  1608. .sp
  1609. The form
  1610. \fI\-\-missing=allow\-any\fR
  1611. will allow object traversal to continue if a missing object is encountered\&. Missing objects will silently be omitted from the results\&.
  1612. .sp
  1613. The form
  1614. \fI\-\-missing=allow\-promisor\fR
  1615. is like
  1616. \fIallow\-any\fR, but will only allow object traversal to continue for EXPECTED promisor missing objects\&. Unexpected missing objects will raise an error\&.
  1617. .sp
  1618. The form
  1619. \fI\-\-missing=print\fR
  1620. is like
  1621. \fIallow\-any\fR, but will also print a list of the missing objects\&. Object IDs are prefixed with a
  1622. \(lq?\(rq
  1623. character\&.
  1624. .sp
  1625. The form
  1626. \fI\-\-missing=print\-info\fR
  1627. is like
  1628. \fIprint\fR, but will also print additional information about the missing object inferred from its containing object\&. The information is all printed on the same line with the missing object ID in the form: ?\fI<oid>\fR
  1629. [\fI<token>\fR\fB=\fR\fI<value>\fR]\&.\&.\&.\&. The
  1630. \fI<token>\fR\fB=\fR\fI<value>\fR
  1631. pairs containing additional information are separated from each other by a SP\&. The value is encoded in a token specific fashion, but SP or LF contained in value are always expected to be represented in such a way that the resulting encoded value does not have either of these two problematic bytes\&. Each
  1632. \fI<token>\fR\fB=\fR\fI<value>\fR
  1633. may be one of the following:
  1634. .sp
  1635. .RS 4
  1636. .ie n \{\
  1637. \h'-04'\(bu\h'+03'\c
  1638. .\}
  1639. .el \{\
  1640. .sp -1
  1641. .IP \(bu 2.3
  1642. .\}
  1643. The
  1644. \fBpath=\fR\fI<path>\fR
  1645. shows the path of the missing object inferred from a containing object\&. A path containing SP or special characters is enclosed in double\-quotes in the C style as needed\&.
  1646. .RE
  1647. .sp
  1648. .RS 4
  1649. .ie n \{\
  1650. \h'-04'\(bu\h'+03'\c
  1651. .\}
  1652. .el \{\
  1653. .sp -1
  1654. .IP \(bu 2.3
  1655. .\}
  1656. The
  1657. \fBtype=\fR\fI<type>\fR
  1658. shows the type of the missing object inferred from a containing object\&.
  1659. .RE
  1660. .sp
  1661. If some tips passed to the traversal are missing, they will be considered as missing too, and the traversal will ignore them\&. In case we cannot get their Object ID though, an error will be raised\&.
  1662. .RE
  1663. .PP
  1664. \-\-exclude\-promisor\-objects
  1665. .RS 4
  1666. (For internal use only\&.) Prefilter object traversal at promisor boundary\&. This is used with partial clone\&. This is stronger than
  1667. \fB\-\-missing=allow\-promisor\fR
  1668. because it limits the traversal, rather than just silencing errors about missing objects\&.
  1669. .RE
  1670. .PP
  1671. \-\-no\-walk[=(sorted|unsorted)]
  1672. .RS 4
  1673. Only show the given commits, but do not traverse their ancestors\&. This has no effect if a range is specified\&. If the argument
  1674. \fBunsorted\fR
  1675. is given, the commits are shown in the order they were given on the command line\&. Otherwise (if
  1676. \fBsorted\fR
  1677. or no argument was given), the commits are shown in reverse chronological order by commit time\&. Cannot be combined with
  1678. \fB\-\-graph\fR\&.
  1679. .RE
  1680. .PP
  1681. \-\-do\-walk
  1682. .RS 4
  1683. Overrides a previous
  1684. \fB\-\-no\-walk\fR\&.
  1685. .RE
  1686. .SS "Commit Formatting"
  1687. .sp
  1688. Using these options, \fBgit-rev-list\fR(1) will act similar to the more specialized family of commit log tools: \fBgit-log\fR(1), \fBgit-show\fR(1), and \fBgit-whatchanged\fR(1)
  1689. .PP
  1690. \-\-pretty[=<format>], \-\-format=<format>
  1691. .RS 4
  1692. Pretty\-print the contents of the commit logs in a given format, where
  1693. \fI<format>\fR
  1694. can be one of
  1695. \fIoneline\fR,
  1696. \fIshort\fR,
  1697. \fImedium\fR,
  1698. \fIfull\fR,
  1699. \fIfuller\fR,
  1700. \fIreference\fR,
  1701. \fIemail\fR,
  1702. \fIraw\fR,
  1703. \fIformat:<string>\fR
  1704. and
  1705. \fItformat:<string>\fR\&. When
  1706. \fI<format>\fR
  1707. is none of the above, and has
  1708. \fI%placeholder\fR
  1709. in it, it acts as if
  1710. \fI\-\-pretty=tformat:<format>\fR
  1711. were given\&.
  1712. .sp
  1713. See the "PRETTY FORMATS" section for some additional details for each format\&. When
  1714. \fI=<format>\fR
  1715. part is omitted, it defaults to
  1716. \fImedium\fR\&.
  1717. .sp
  1718. Note: you can specify the default pretty format in the repository configuration (see
  1719. \fBgit-config\fR(1))\&.
  1720. .RE
  1721. .PP
  1722. \-\-abbrev\-commit
  1723. .RS 4
  1724. Instead of showing the full 40\-byte hexadecimal commit object name, show a prefix that names the object uniquely\&. "\-\-abbrev=<n>" (which also modifies diff output, if it is displayed) option can be used to specify the minimum length of the prefix\&.
  1725. .sp
  1726. This should make "\-\-pretty=oneline" a whole lot more readable for people using 80\-column terminals\&.
  1727. .RE
  1728. .PP
  1729. \-\-no\-abbrev\-commit
  1730. .RS 4
  1731. Show the full 40\-byte hexadecimal commit object name\&. This negates
  1732. \fB\-\-abbrev\-commit\fR, either explicit or implied by other options such as "\-\-oneline"\&. It also overrides the
  1733. \fBlog\&.abbrevCommit\fR
  1734. variable\&.
  1735. .RE
  1736. .PP
  1737. \-\-oneline
  1738. .RS 4
  1739. This is a shorthand for "\-\-pretty=oneline \-\-abbrev\-commit" used together\&.
  1740. .RE
  1741. .PP
  1742. \-\-encoding=<encoding>
  1743. .RS 4
  1744. Commit objects record the character encoding used for the log message in their encoding header; this option can be used to tell the command to re\-code the commit log message in the encoding preferred by the user\&. For non plumbing commands this defaults to UTF\-8\&. Note that if an object claims to be encoded in
  1745. \fBX\fR
  1746. and we are outputting in
  1747. \fBX\fR, we will output the object verbatim; this means that invalid sequences in the original commit may be copied to the output\&. Likewise, if iconv(3) fails to convert the commit, we will quietly output the original object verbatim\&.
  1748. .RE
  1749. .PP
  1750. \-\-expand\-tabs=<n>, \-\-expand\-tabs, \-\-no\-expand\-tabs
  1751. .RS 4
  1752. Perform a tab expansion (replace each tab with enough spaces to fill to the next display column that is a multiple of
  1753. \fI<n>\fR) in the log message before showing it in the output\&.
  1754. \fB\-\-expand\-tabs\fR
  1755. is a short\-hand for
  1756. \fB\-\-expand\-tabs=8\fR, and
  1757. \fB\-\-no\-expand\-tabs\fR
  1758. is a short\-hand for
  1759. \fB\-\-expand\-tabs=0\fR, which disables tab expansion\&.
  1760. .sp
  1761. By default, tabs are expanded in pretty formats that indent the log message by 4 spaces (i\&.e\&.
  1762. \fImedium\fR, which is the default,
  1763. \fIfull\fR, and
  1764. \fIfuller\fR)\&.
  1765. .RE
  1766. .PP
  1767. \-\-show\-signature
  1768. .RS 4
  1769. Check the validity of a signed commit object by passing the signature to
  1770. \fBgpg\fR
  1771. \fB\-\-verify\fR
  1772. and show the output\&.
  1773. .RE
  1774. .PP
  1775. \-\-relative\-date
  1776. .RS 4
  1777. Synonym for
  1778. \fB\-\-date=relative\fR\&.
  1779. .RE
  1780. .PP
  1781. \-\-date=<format>
  1782. .RS 4
  1783. Only takes effect for dates shown in human\-readable format, such as when using
  1784. \fB\-\-pretty\fR\&.
  1785. \fBlog\&.date\fR
  1786. config variable sets a default value for the log command\(cqs
  1787. \fB\-\-date\fR
  1788. option\&. By default, dates are shown in the original time zone (either committer\(cqs or author\(cqs)\&. If
  1789. \fB\-local\fR
  1790. is appended to the format (e\&.g\&.,
  1791. \fBiso\-local\fR), the user\(cqs local time zone is used instead\&.
  1792. .sp
  1793. \fB\-\-date=relative\fR
  1794. shows dates relative to the current time, e\&.g\&.
  1795. \(lq2 hours ago\(rq\&. The
  1796. \fB\-local\fR
  1797. option has no effect for
  1798. \fB\-\-date=relative\fR\&.
  1799. .sp
  1800. \fB\-\-date=local\fR
  1801. is an alias for
  1802. \fB\-\-date=default\-local\fR\&.
  1803. .sp
  1804. \fB\-\-date=iso\fR
  1805. (or
  1806. \fB\-\-date=iso8601\fR) shows timestamps in a ISO 8601\-like format\&. The differences to the strict ISO 8601 format are:
  1807. .sp
  1808. .RS 4
  1809. .ie n \{\
  1810. \h'-04'\(bu\h'+03'\c
  1811. .\}
  1812. .el \{\
  1813. .sp -1
  1814. .IP \(bu 2.3
  1815. .\}
  1816. a space instead of the
  1817. \fBT\fR
  1818. date/time delimiter
  1819. .RE
  1820. .sp
  1821. .RS 4
  1822. .ie n \{\
  1823. \h'-04'\(bu\h'+03'\c
  1824. .\}
  1825. .el \{\
  1826. .sp -1
  1827. .IP \(bu 2.3
  1828. .\}
  1829. a space between time and time zone
  1830. .RE
  1831. .sp
  1832. .RS 4
  1833. .ie n \{\
  1834. \h'-04'\(bu\h'+03'\c
  1835. .\}
  1836. .el \{\
  1837. .sp -1
  1838. .IP \(bu 2.3
  1839. .\}
  1840. no colon between hours and minutes of the time zone
  1841. .RE
  1842. .sp
  1843. \fB\-\-date=iso\-strict\fR
  1844. (or
  1845. \fB\-\-date=iso8601\-strict\fR) shows timestamps in strict ISO 8601 format\&.
  1846. .sp
  1847. \fB\-\-date=rfc\fR
  1848. (or
  1849. \fB\-\-date=rfc2822\fR) shows timestamps in RFC 2822 format, often found in email messages\&.
  1850. .sp
  1851. \fB\-\-date=short\fR
  1852. shows only the date, but not the time, in
  1853. \fBYYYY\-MM\-DD\fR
  1854. format\&.
  1855. .sp
  1856. \fB\-\-date=raw\fR
  1857. shows the date as seconds since the epoch (1970\-01\-01 00:00:00 UTC), followed by a space, and then the timezone as an offset from UTC (a
  1858. \fB+\fR
  1859. or
  1860. \fB\-\fR
  1861. with four digits; the first two are hours, and the second two are minutes)\&. I\&.e\&., as if the timestamp were formatted with
  1862. \fBstrftime\fR("%s %z"))\&. Note that the
  1863. \fB\-local\fR
  1864. option does not affect the seconds\-since\-epoch value (which is always measured in UTC), but does switch the accompanying timezone value\&.
  1865. .sp
  1866. \fB\-\-date=human\fR
  1867. shows the timezone if the timezone does not match the current time\-zone, and doesn\(cqt print the whole date if that matches (ie skip printing year for dates that are "this year", but also skip the whole date itself if it\(cqs in the last few days and we can just say what weekday it was)\&. For older dates the hour and minute is also omitted\&.
  1868. .sp
  1869. \fB\-\-date=unix\fR
  1870. shows the date as a Unix epoch timestamp (seconds since 1970)\&. As with
  1871. \fB\-\-raw\fR, this is always in UTC and therefore
  1872. \fB\-local\fR
  1873. has no effect\&.
  1874. .sp
  1875. \fB\-\-date=format:\&.\&.\fR\&. feeds the format \&.\&.\&. to your system
  1876. \fBstrftime\fR, except for %s, %z, and %Z, which are handled internally\&. Use
  1877. \fB\-\-date=format:\fR%c to show the date in your system locale\(cqs preferred format\&. See the
  1878. \fBstrftime\fR
  1879. manual for a complete list of format placeholders\&. When using
  1880. \fB\-local\fR, the correct syntax is
  1881. \fB\-\-date=format\-local:\&.\&.\fR\&.\&.
  1882. .sp
  1883. \fB\-\-date=default\fR
  1884. is the default format, and is based on ctime(3) output\&. It shows a single line with three\-letter day of the week, three\-letter month, day\-of\-month, hour\-minute\-seconds in "HH:MM:SS" format, followed by 4\-digit year, plus timezone information, unless the local time zone is used, e\&.g\&.
  1885. \fBThu\fR
  1886. \fBJan\fR
  1887. \fB1\fR
  1888. \fB00:00:00\fR
  1889. \fB1970\fR
  1890. \fB+0000\fR\&.
  1891. .RE
  1892. .PP
  1893. \-\-header
  1894. .RS 4
  1895. Print the contents of the commit in raw\-format; each record is separated with a NUL character\&.
  1896. .RE
  1897. .PP
  1898. \-\-no\-commit\-header
  1899. .RS 4
  1900. Suppress the header line containing "commit" and the object ID printed before the specified format\&. This has no effect on the built\-in formats; only custom formats are affected\&.
  1901. .RE
  1902. .PP
  1903. \-\-commit\-header
  1904. .RS 4
  1905. Overrides a previous
  1906. \fB\-\-no\-commit\-header\fR\&.
  1907. .RE
  1908. .PP
  1909. \-\-parents
  1910. .RS 4
  1911. Print also the parents of the commit (in the form "commit parent\&...\:")\&. Also enables parent rewriting, see
  1912. \fIHistory Simplification\fR
  1913. above\&.
  1914. .RE
  1915. .PP
  1916. \-\-children
  1917. .RS 4
  1918. Print also the children of the commit (in the form "commit child\&...\:")\&. Also enables parent rewriting, see
  1919. \fIHistory Simplification\fR
  1920. above\&.
  1921. .RE
  1922. .PP
  1923. \-\-timestamp
  1924. .RS 4
  1925. Print the raw commit timestamp\&.
  1926. .RE
  1927. .PP
  1928. \-\-left\-right
  1929. .RS 4
  1930. Mark which side of a symmetric difference a commit is reachable from\&. Commits from the left side are prefixed with < and those from the right with >\&. If combined with
  1931. \fB\-\-boundary\fR, those commits are prefixed with
  1932. \fB\-\fR\&.
  1933. .sp
  1934. For example, if you have this topology:
  1935. .sp
  1936. .if n \{\
  1937. .RS 4
  1938. .\}
  1939. .nf
  1940.              y\-\-\-b\-\-\-b  branch B
  1941.             / \e /
  1942.            /   \&.
  1943.           /   / \e
  1944.          o\-\-\-x\-\-\-a\-\-\-a  branch A
  1945. .fi
  1946. .if n \{\
  1947. .RE
  1948. .\}
  1949. .sp
  1950. you would get an output like this:
  1951. .sp
  1952. .if n \{\
  1953. .RS 4
  1954. .\}
  1955. .nf
  1956.         $ git rev\-list \-\-left\-right \-\-boundary \-\-pretty=oneline A\&.\&.\&.B
  1958.         >bbbbbbb\&.\&.\&. 3rd on b
  1959.         >bbbbbbb\&.\&.\&. 2nd on b
  1960.         <aaaaaaa\&.\&.\&. 3rd on a
  1961.         <aaaaaaa\&.\&.\&. 2nd on a
  1962.         \-yyyyyyy\&.\&.\&. 1st on b
  1963.         \-xxxxxxx\&.\&.\&. 1st on a
  1964. .fi
  1965. .if n \{\
  1966. .RE
  1967. .\}
  1968. .RE
  1969. .PP
  1970. \-\-graph
  1971. .RS 4
  1972. Draw a text\-based graphical representation of the commit history on the left hand side of the output\&. This may cause extra lines to be printed in between commits, in order for the graph history to be drawn properly\&. Cannot be combined with
  1973. \fB\-\-no\-walk\fR\&.
  1974. .sp
  1975. This enables parent rewriting, see
  1976. \fIHistory Simplification\fR
  1977. above\&.
  1978. .sp
  1979. This implies the
  1980. \fB\-\-topo\-order\fR
  1981. option by default, but the
  1982. \fB\-\-date\-order\fR
  1983. option may also be specified\&.
  1984. .RE
  1985. .PP
  1986. \-\-show\-linear\-break[=<barrier>]
  1987. .RS 4
  1988. When \-\-graph is not used, all history branches are flattened which can make it hard to see that the two consecutive commits do not belong to a linear branch\&. This option puts a barrier in between them in that case\&. If
  1989. \fI<barrier>\fR
  1990. is specified, it is the string that will be shown instead of the default one\&.
  1991. .RE
  1992. .PP
  1993. \-\-count
  1994. .RS 4
  1995. Print a number stating how many commits would have been listed, and suppress all other output\&. When used together with
  1996. \fB\-\-left\-right\fR, instead print the counts for left and right commits, separated by a tab\&. When used together with
  1997. \fB\-\-cherry\-mark\fR, omit patch equivalent commits from these counts and print the count for equivalent commits separated by a tab\&.
  1998. .RE
  1999. .SH "PRETTY FORMATS"
  2000. .sp
  2001. If the commit is a merge, and if the pretty\-format is not \fIoneline\fR, \fIemail\fR or \fIraw\fR, an additional line is inserted before the \fIAuthor:\fR line\&. This line begins with "Merge: " and the hashes of ancestral commits are printed, separated by spaces\&. Note that the listed commits may not necessarily be the list of the \fBdirect\fR parent commits if you have limited your view of history: for example, if you are only interested in changes related to a certain directory or file\&.
  2002. .sp
  2003. There are several built\-in formats, and you can define additional formats by setting a pretty\&.<name> config option to either another format name, or a \fIformat:\fR string, as described below (see \fBgit-config\fR(1))\&. Here are the details of the built\-in formats:
  2004. .sp
  2005. .RS 4
  2006. .ie n \{\
  2007. \h'-04'\(bu\h'+03'\c
  2008. .\}
  2009. .el \{\
  2010. .sp -1
  2011. .IP \(bu 2.3
  2012. .\}
  2013. \fIoneline\fR
  2014. .sp
  2015. .if n \{\
  2016. .RS 4
  2017. .\}
  2018. .nf
  2019. <hash> <title\-line>
  2020. .fi
  2021. .if n \{\
  2022. .RE
  2023. .\}
  2024. .sp
  2025. This is designed to be as compact as possible\&.
  2026. .RE
  2027. .sp
  2028. .RS 4
  2029. .ie n \{\
  2030. \h'-04'\(bu\h'+03'\c
  2031. .\}
  2032. .el \{\
  2033. .sp -1
  2034. .IP \(bu 2.3
  2035. .\}
  2036. \fIshort\fR
  2037. .sp
  2038. .if n \{\
  2039. .RS 4
  2040. .\}
  2041. .nf
  2042. commit <hash>
  2043. Author: <author>
  2044. .fi
  2045. .if n \{\
  2046. .RE
  2047. .\}
  2048. .sp
  2049. .if n \{\
  2050. .RS 4
  2051. .\}
  2052. .nf
  2053. <title\-line>
  2054. .fi
  2055. .if n \{\
  2056. .RE
  2057. .\}
  2058. .RE
  2059. .sp
  2060. .RS 4
  2061. .ie n \{\
  2062. \h'-04'\(bu\h'+03'\c
  2063. .\}
  2064. .el \{\
  2065. .sp -1
  2066. .IP \(bu 2.3
  2067. .\}
  2068. \fImedium\fR
  2069. .sp
  2070. .if n \{\
  2071. .RS 4
  2072. .\}
  2073. .nf
  2074. commit <hash>
  2075. Author: <author>
  2076. Date:   <author\-date>
  2077. .fi
  2078. .if n \{\
  2079. .RE
  2080. .\}
  2081. .sp
  2082. .if n \{\
  2083. .RS 4
  2084. .\}
  2085. .nf
  2086. <title\-line>
  2087. .fi
  2088. .if n \{\
  2089. .RE
  2090. .\}
  2091. .sp
  2092. .if n \{\
  2093. .RS 4
  2094. .\}
  2095. .nf
  2096. <full\-commit\-message>
  2097. .fi
  2098. .if n \{\
  2099. .RE
  2100. .\}
  2101. .RE
  2102. .sp
  2103. .RS 4
  2104. .ie n \{\
  2105. \h'-04'\(bu\h'+03'\c
  2106. .\}
  2107. .el \{\
  2108. .sp -1
  2109. .IP \(bu 2.3
  2110. .\}
  2111. \fIfull\fR
  2112. .sp
  2113. .if n \{\
  2114. .RS 4
  2115. .\}
  2116. .nf
  2117. commit <hash>
  2118. Author: <author>
  2119. Commit: <committer>
  2120. .fi
  2121. .if n \{\
  2122. .RE
  2123. .\}
  2124. .sp
  2125. .if n \{\
  2126. .RS 4
  2127. .\}
  2128. .nf
  2129. <title\-line>
  2130. .fi
  2131. .if n \{\
  2132. .RE
  2133. .\}
  2134. .sp
  2135. .if n \{\
  2136. .RS 4
  2137. .\}
  2138. .nf
  2139. <full\-commit\-message>
  2140. .fi
  2141. .if n \{\
  2142. .RE
  2143. .\}
  2144. .RE
  2145. .sp
  2146. .RS 4
  2147. .ie n \{\
  2148. \h'-04'\(bu\h'+03'\c
  2149. .\}
  2150. .el \{\
  2151. .sp -1
  2152. .IP \(bu 2.3
  2153. .\}
  2154. \fIfuller\fR
  2155. .sp
  2156. .if n \{\
  2157. .RS 4
  2158. .\}
  2159. .nf
  2160. commit <hash>
  2161. Author:     <author>
  2162. AuthorDate: <author\-date>
  2163. Commit:     <committer>
  2164. CommitDate: <committer\-date>
  2165. .fi
  2166. .if n \{\
  2167. .RE
  2168. .\}
  2169. .sp
  2170. .if n \{\
  2171. .RS 4
  2172. .\}
  2173. .nf
  2174. <title\-line>
  2175. .fi
  2176. .if n \{\
  2177. .RE
  2178. .\}
  2179. .sp
  2180. .if n \{\
  2181. .RS 4
  2182. .\}
  2183. .nf
  2184. <full\-commit\-message>
  2185. .fi
  2186. .if n \{\
  2187. .RE
  2188. .\}
  2189. .RE
  2190. .sp
  2191. .RS 4
  2192. .ie n \{\
  2193. \h'-04'\(bu\h'+03'\c
  2194. .\}
  2195. .el \{\
  2196. .sp -1
  2197. .IP \(bu 2.3
  2198. .\}
  2199. \fIreference\fR
  2200. .sp
  2201. .if n \{\
  2202. .RS 4
  2203. .\}
  2204. .nf
  2205. <abbrev\-hash> (<title\-line>, <short\-author\-date>)
  2206. .fi
  2207. .if n \{\
  2208. .RE
  2209. .\}
  2210. .sp
  2211. This format is used to refer to another commit in a commit message and is the same as
  2212. \fB\-\-pretty=\fR\*(Aqformat:%C(\fBauto\fR)%h (%s, %ad)\*(Aq\&. By default, the date is formatted with
  2213. \fB\-\-date=short\fR
  2214. unless another
  2215. \fB\-\-date\fR
  2216. option is explicitly specified\&. As with any
  2217. \fBformat:\fR
  2218. with format placeholders, its output is not affected by other options like
  2219. \fB\-\-decorate\fR
  2220. and
  2221. \fB\-\-walk\-reflogs\fR\&.
  2222. .RE
  2223. .sp
  2224. .RS 4
  2225. .ie n \{\
  2226. \h'-04'\(bu\h'+03'\c
  2227. .\}
  2228. .el \{\
  2229. .sp -1
  2230. .IP \(bu 2.3
  2231. .\}
  2232. \fIemail\fR
  2233. .sp
  2234. .if n \{\
  2235. .RS 4
  2236. .\}
  2237. .nf
  2238. From <hash> <date>
  2239. From: <author>
  2240. Date: <author\-date>
  2241. Subject: [PATCH] <title\-line>
  2242. .fi
  2243. .if n \{\
  2244. .RE
  2245. .\}
  2246. .sp
  2247. .if n \{\
  2248. .RS 4
  2249. .\}
  2250. .nf
  2251. <full\-commit\-message>
  2252. .fi
  2253. .if n \{\
  2254. .RE
  2255. .\}
  2256. .RE
  2257. .sp
  2258. .RS 4
  2259. .ie n \{\
  2260. \h'-04'\(bu\h'+03'\c
  2261. .\}
  2262. .el \{\
  2263. .sp -1
  2264. .IP \(bu 2.3
  2265. .\}
  2266. \fImboxrd\fR
  2267. .sp
  2268. Like
  2269. \fIemail\fR, but lines in the commit message starting with "From " (preceded by zero or more ">") are quoted with ">" so they aren\(cqt confused as starting a new commit\&.
  2270. .RE
  2271. .sp
  2272. .RS 4
  2273. .ie n \{\
  2274. \h'-04'\(bu\h'+03'\c
  2275. .\}
  2276. .el \{\
  2277. .sp -1
  2278. .IP \(bu 2.3
  2279. .\}
  2280. \fIraw\fR
  2281. .sp
  2282. The
  2283. \fIraw\fR
  2284. format shows the entire commit exactly as stored in the commit object\&. Notably, the hashes are displayed in full, regardless of whether \-\-abbrev or \-\-no\-abbrev are used, and
  2285. \fIparents\fR
  2286. information show the true parent commits, without taking grafts or history simplification into account\&. Note that this format affects the way commits are displayed, but not the way the diff is shown e\&.g\&. with
  2287. \fBgit\fR
  2288. \fBlog\fR
  2289. \fB\-\-raw\fR\&. To get full object names in a raw diff format, use
  2290. \fB\-\-no\-abbrev\fR\&.
  2291. .RE
  2292. .sp
  2293. .RS 4
  2294. .ie n \{\
  2295. \h'-04'\(bu\h'+03'\c
  2296. .\}
  2297. .el \{\
  2298. .sp -1
  2299. .IP \(bu 2.3
  2300. .\}
  2301. \fIformat:<format\-string>\fR
  2302. .sp
  2303. The
  2304. \fIformat:<format\-string>\fR
  2305. format allows you to specify which information you want to show\&. It works a little bit like printf format, with the notable exception that you get a newline with
  2306. \fI%n\fR
  2307. instead of
  2308. \fI\en\fR\&.
  2309. .sp
  2310. E\&.g,
  2311. \fIformat:"The author of %h was %an, %ar%nThe title was >>%s<<%n"\fR
  2312. would show something like this:
  2313. .sp
  2314. .if n \{\
  2315. .RS 4
  2316. .\}
  2317. .nf
  2318. The author of fe6e0ee was Junio C Hamano, 23 hours ago
  2319. The title was >>t4119: test autocomputing \-p<n> for traditional diff input\&.<<
  2320. .fi
  2321. .if n \{\
  2322. .RE
  2323. .\}
  2324. .sp
  2325. The placeholders are:
  2326. .sp
  2327. .RS 4
  2328. .ie n \{\
  2329. \h'-04'\(bu\h'+03'\c
  2330. .\}
  2331. .el \{\
  2332. .sp -1
  2333. .IP \(bu 2.3
  2334. .\}
  2335. Placeholders that expand to a single literal character:
  2336. .PP
  2337. \fI%n\fR
  2338. .RS 4
  2339. newline
  2340. .RE
  2341. .PP
  2342. \fI%%\fR
  2343. .RS 4
  2344. a raw
  2345. \fI%\fR
  2346. .RE
  2347. .PP
  2348. \fI%x00\fR
  2349. .RS 4
  2350. \fI%x\fR
  2351. followed by two hexadecimal digits is replaced with a byte with the hexadecimal digits\*(Aq value (we will call this "literal formatting code" in the rest of this document)\&.
  2352. .RE
  2353. .RE
  2354. .sp
  2355. .RS 4
  2356. .ie n \{\
  2357. \h'-04'\(bu\h'+03'\c
  2358. .\}
  2359. .el \{\
  2360. .sp -1
  2361. .IP \(bu 2.3
  2362. .\}
  2363. Placeholders that affect formatting of later placeholders:
  2364. .PP
  2365. \fI%Cred\fR
  2366. .RS 4
  2367. switch color to red
  2368. .RE
  2369. .PP
  2370. \fI%Cgreen\fR
  2371. .RS 4
  2372. switch color to green
  2373. .RE
  2374. .PP
  2375. \fI%Cblue\fR
  2376. .RS 4
  2377. switch color to blue
  2378. .RE
  2379. .PP
  2380. \fI%Creset\fR
  2381. .RS 4
  2382. reset color
  2383. .RE
  2384. .PP
  2385. \fI%C(\&...\:)\fR
  2386. .RS 4
  2387. color specification, as described under Values in the "CONFIGURATION FILE" section of
  2388. \fBgit-config\fR(1)\&. By default, colors are shown only when enabled for log output (by
  2389. \fBcolor\&.diff\fR,
  2390. \fBcolor\&.ui\fR, or
  2391. \fB\-\-color\fR, and respecting the
  2392. \fBauto\fR
  2393. settings of the former if we are going to a terminal)\&. %C(\fBauto,\fR\fB\&.\&.\&.\fR) is accepted as a historical synonym for the default (e\&.g\&., %C(\fBauto,red\fR))\&. Specifying %C(\fBalways,\fR\fB\&.\&.\&.\fR) will show the colors even when color is not otherwise enabled (though consider just using
  2394. \fB\-\-color=always\fR
  2395. to enable color for the whole output, including this format and anything else git might color)\&.
  2396. \fBauto\fR
  2397. alone (i\&.e\&. %C(\fBauto\fR)) will turn on auto coloring on the next placeholders until the color is switched again\&.
  2398. .RE
  2399. .PP
  2400. \fI%m\fR
  2401. .RS 4
  2402. left (<), right (>) or boundary (\fB\-\fR) mark
  2403. .RE
  2404. .PP
  2405. \fI%w([<w>[,<i1>[,<i2>]]])\fR
  2406. .RS 4
  2407. switch line wrapping, like the \-w option of
  2408. \fBgit-shortlog\fR(1)\&.
  2409. .RE
  2410. .PP
  2411. \fI%<( <N> [,trunc|ltrunc|mtrunc])\fR
  2412. .RS 4
  2413. make the next placeholder take at least N column widths, padding spaces on the right if necessary\&. Optionally truncate (with ellipsis
  2414. \fI\&.\&.\fR) at the left (ltrunc)
  2415. \fB\&.\&.\fR\fBft\fR, the middle (mtrunc)
  2416. \fBmi\fR\fB\&.\&.\fR\fBle\fR, or the end (trunc)
  2417. \fBrig\&.\&.\fR, if the output is longer than N columns\&. Note 1: that truncating only works correctly with N >= 2\&. Note 2: spaces around the N and M (see below) values are optional\&. Note 3: Emojis and other wide characters will take two display columns, which may over\-run column boundaries\&. Note 4: decomposed character combining marks may be misplaced at padding boundaries\&.
  2418. .RE
  2419. .PP
  2420. \fI%<|( <M> )\fR
  2421. .RS 4
  2422. make the next placeholder take at least until Mth display column, padding spaces on the right if necessary\&. Use negative M values for column positions measured from the right hand edge of the terminal window\&.
  2423. .RE
  2424. .PP
  2425. \fI%>( <N> )\fR, \fI%>|( <M> )\fR
  2426. .RS 4
  2427. similar to
  2428. \fI%<( <N> )\fR,
  2429. \fI%<|( <M> )\fR
  2430. respectively, but padding spaces on the left
  2431. .RE
  2432. .PP
  2433. \fI%>>( <N> )\fR, \fI%>>|( <M> )\fR
  2434. .RS 4
  2435. similar to
  2436. \fI%>( <N> )\fR,
  2437. \fI%>|( <M> )\fR
  2438. respectively, except that if the next placeholder takes more spaces than given and there are spaces on its left, use those spaces
  2439. .RE
  2440. .PP
  2441. \fI%><( <N> )\fR, \fI%><|( <M> )\fR
  2442. .RS 4
  2443. similar to
  2444. \fI%<( <N> )\fR,
  2445. \fI%<|( <M> )\fR
  2446. respectively, but padding both sides (i\&.e\&. the text is centered)
  2447. .RE
  2448. .RE
  2449. .sp
  2450. .RS 4
  2451. .ie n \{\
  2452. \h'-04'\(bu\h'+03'\c
  2453. .\}
  2454. .el \{\
  2455. .sp -1
  2456. .IP \(bu 2.3
  2457. .\}
  2458. Placeholders that expand to information extracted from the commit:
  2459. .PP
  2460. \fI%H\fR
  2461. .RS 4
  2462. commit hash
  2463. .RE
  2464. .PP
  2465. \fI%h\fR
  2466. .RS 4
  2467. abbreviated commit hash
  2468. .RE
  2469. .PP
  2470. \fI%T\fR
  2471. .RS 4
  2472. tree hash
  2473. .RE
  2474. .PP
  2475. \fI%t\fR
  2476. .RS 4
  2477. abbreviated tree hash
  2478. .RE
  2479. .PP
  2480. \fI%P\fR
  2481. .RS 4
  2482. parent hashes
  2483. .RE
  2484. .PP
  2485. \fI%p\fR
  2486. .RS 4
  2487. abbreviated parent hashes
  2488. .RE
  2489. .PP
  2490. \fI%an\fR
  2491. .RS 4
  2492. author name
  2493. .RE
  2494. .PP
  2495. \fI%aN\fR
  2496. .RS 4
  2497. author name (respecting \&.mailmap, see
  2498. \fBgit-shortlog\fR(1)
  2499. or
  2500. \fBgit-blame\fR(1))
  2501. .RE
  2502. .PP
  2503. \fI%ae\fR
  2504. .RS 4
  2505. author email
  2506. .RE
  2507. .PP
  2508. \fI%aE\fR
  2509. .RS 4
  2510. author email (respecting \&.mailmap, see
  2511. \fBgit-shortlog\fR(1)
  2512. or
  2513. \fBgit-blame\fR(1))
  2514. .RE
  2515. .PP
  2516. \fI%al\fR
  2517. .RS 4
  2518. author email local\-part (the part before the
  2519. \fI@\fR
  2520. sign)
  2521. .RE
  2522. .PP
  2523. \fI%aL\fR
  2524. .RS 4
  2525. author local\-part (see
  2526. \fI%al\fR) respecting \&.mailmap, see
  2527. \fBgit-shortlog\fR(1)
  2528. or
  2529. \fBgit-blame\fR(1))
  2530. .RE
  2531. .PP
  2532. \fI%ad\fR
  2533. .RS 4
  2534. author date (format respects \-\-date= option)
  2535. .RE
  2536. .PP
  2537. \fI%aD\fR
  2538. .RS 4
  2539. author date, RFC2822 style
  2540. .RE
  2541. .PP
  2542. \fI%ar\fR
  2543. .RS 4
  2544. author date, relative
  2545. .RE
  2546. .PP
  2547. \fI%at\fR
  2548. .RS 4
  2549. author date, UNIX timestamp
  2550. .RE
  2551. .PP
  2552. \fI%ai\fR
  2553. .RS 4
  2554. author date, ISO 8601\-like format
  2555. .RE
  2556. .PP
  2557. \fI%aI\fR
  2558. .RS 4
  2559. author date, strict ISO 8601 format
  2560. .RE
  2561. .PP
  2562. \fI%as\fR
  2563. .RS 4
  2564. author date, short format (\fBYYYY\-MM\-DD\fR)
  2565. .RE
  2566. .PP
  2567. \fI%ah\fR
  2568. .RS 4
  2569. author date, human style (like the
  2570. \fB\-\-date=human\fR
  2571. option of
  2572. \fBgit-rev-list\fR(1))
  2573. .RE
  2574. .PP
  2575. \fI%cn\fR
  2576. .RS 4
  2577. committer name
  2578. .RE
  2579. .PP
  2580. \fI%cN\fR
  2581. .RS 4
  2582. committer name (respecting \&.mailmap, see
  2583. \fBgit-shortlog\fR(1)
  2584. or
  2585. \fBgit-blame\fR(1))
  2586. .RE
  2587. .PP
  2588. \fI%ce\fR
  2589. .RS 4
  2590. committer email
  2591. .RE
  2592. .PP
  2593. \fI%cE\fR
  2594. .RS 4
  2595. committer email (respecting \&.mailmap, see
  2596. \fBgit-shortlog\fR(1)
  2597. or
  2598. \fBgit-blame\fR(1))
  2599. .RE
  2600. .PP
  2601. \fI%cl\fR
  2602. .RS 4
  2603. committer email local\-part (the part before the
  2604. \fI@\fR
  2605. sign)
  2606. .RE
  2607. .PP
  2608. \fI%cL\fR
  2609. .RS 4
  2610. committer local\-part (see
  2611. \fI%cl\fR) respecting \&.mailmap, see
  2612. \fBgit-shortlog\fR(1)
  2613. or
  2614. \fBgit-blame\fR(1))
  2615. .RE
  2616. .PP
  2617. \fI%cd\fR
  2618. .RS 4
  2619. committer date (format respects \-\-date= option)
  2620. .RE
  2621. .PP
  2622. \fI%cD\fR
  2623. .RS 4
  2624. committer date, RFC2822 style
  2625. .RE
  2626. .PP
  2627. \fI%cr\fR
  2628. .RS 4
  2629. committer date, relative
  2630. .RE
  2631. .PP
  2632. \fI%ct\fR
  2633. .RS 4
  2634. committer date, UNIX timestamp
  2635. .RE
  2636. .PP
  2637. \fI%ci\fR
  2638. .RS 4
  2639. committer date, ISO 8601\-like format
  2640. .RE
  2641. .PP
  2642. \fI%cI\fR
  2643. .RS 4
  2644. committer date, strict ISO 8601 format
  2645. .RE
  2646. .PP
  2647. \fI%cs\fR
  2648. .RS 4
  2649. committer date, short format (\fBYYYY\-MM\-DD\fR)
  2650. .RE
  2651. .PP
  2652. \fI%ch\fR
  2653. .RS 4
  2654. committer date, human style (like the
  2655. \fB\-\-date=human\fR
  2656. option of
  2657. \fBgit-rev-list\fR(1))
  2658. .RE
  2659. .PP
  2660. \fI%d\fR
  2661. .RS 4
  2662. ref names, like the \-\-decorate option of
  2663. \fBgit-log\fR(1)
  2664. .RE
  2665. .PP
  2666. \fI%D\fR
  2667. .RS 4
  2668. ref names without the " (", ")" wrapping\&.
  2669. .RE
  2670. .PP
  2671. \fI%(decorate[:<options>])\fR
  2672. .RS 4
  2673. ref names with custom decorations\&. The
  2674. \fBdecorate\fR
  2675. string may be followed by a colon and zero or more comma\-separated options\&. Option values may contain literal formatting codes\&. These must be used for commas (%x2C) and closing parentheses (%x29), due to their role in the option syntax\&.
  2676. .sp
  2677. .RS 4
  2678. .ie n \{\
  2679. \h'-04'\(bu\h'+03'\c
  2680. .\}
  2681. .el \{\
  2682. .sp -1
  2683. .IP \(bu 2.3
  2684. .\}
  2685. \fIprefix=<value>\fR: Shown before the list of ref names\&. Defaults to "\ \&("\&.
  2686. .RE
  2687. .sp
  2688. .RS 4
  2689. .ie n \{\
  2690. \h'-04'\(bu\h'+03'\c
  2691. .\}
  2692. .el \{\
  2693. .sp -1
  2694. .IP \(bu 2.3
  2695. .\}
  2696. \fIsuffix=<value>\fR: Shown after the list of ref names\&. Defaults to ")"\&.
  2697. .RE
  2698. .sp
  2699. .RS 4
  2700. .ie n \{\
  2701. \h'-04'\(bu\h'+03'\c
  2702. .\}
  2703. .el \{\
  2704. .sp -1
  2705. .IP \(bu 2.3
  2706. .\}
  2707. \fIseparator=<value>\fR: Shown between ref names\&. Defaults to "\fB,\fR\ \&"\&.
  2708. .RE
  2709. .sp
  2710. .RS 4
  2711. .ie n \{\
  2712. \h'-04'\(bu\h'+03'\c
  2713. .\}
  2714. .el \{\
  2715. .sp -1
  2716. .IP \(bu 2.3
  2717. .\}
  2718. \fIpointer=<value>\fR: Shown between HEAD and the branch it points to, if any\&. Defaults to "\ \&\fB\-\fR>\ \&"\&.
  2719. .RE
  2720. .sp
  2721. .RS 4
  2722. .ie n \{\
  2723. \h'-04'\(bu\h'+03'\c
  2724. .\}
  2725. .el \{\
  2726. .sp -1
  2727. .IP \(bu 2.3
  2728. .\}
  2729. \fItag=<value>\fR: Shown before tag names\&. Defaults to "\fBtag:\fR\ \&"\&.
  2730. .RE
  2731. .RE
  2732. .RE
  2733. .sp
  2734. For example, to produce decorations with no wrapping or tag annotations, and spaces as separators:
  2735. .sp
  2736. + %(\fBdecorate:prefix=,suffix=,tag=,separator=\fR
  2737. )
  2738. .PP
  2739. \fI%(describe[:<options>])\fR
  2740. .RS 4
  2741. human\-readable name, like
  2742. \fBgit-describe\fR(1); empty string for undescribable commits\&. The
  2743. \fBdescribe\fR
  2744. string may be followed by a colon and zero or more comma\-separated options\&. Descriptions can be inconsistent when tags are added or removed at the same time\&.
  2745. .sp
  2746. .RS 4
  2747. .ie n \{\
  2748. \h'-04'\(bu\h'+03'\c
  2749. .\}
  2750. .el \{\
  2751. .sp -1
  2752. .IP \(bu 2.3
  2753. .\}
  2754. \fItags[=<bool\-value>]\fR: Instead of only considering annotated tags, consider lightweight tags as well\&.
  2755. .RE
  2756. .sp
  2757. .RS 4
  2758. .ie n \{\
  2759. \h'-04'\(bu\h'+03'\c
  2760. .\}
  2761. .el \{\
  2762. .sp -1
  2763. .IP \(bu 2.3
  2764. .\}
  2765. \fIabbrev=<number>\fR: Instead of using the default number of hexadecimal digits (which will vary according to the number of objects in the repository with a default of 7) of the abbreviated object name, use <number> digits, or as many digits as needed to form a unique object name\&.
  2766. .RE
  2767. .sp
  2768. .RS 4
  2769. .ie n \{\
  2770. \h'-04'\(bu\h'+03'\c
  2771. .\}
  2772. .el \{\
  2773. .sp -1
  2774. .IP \(bu 2.3
  2775. .\}
  2776. \fImatch=<pattern>\fR: Only consider tags matching the given
  2777. \fBglob\fR(\fB7\fR) pattern, excluding the "refs/tags/" prefix\&.
  2778. .RE
  2779. .sp
  2780. .RS 4
  2781. .ie n \{\
  2782. \h'-04'\(bu\h'+03'\c
  2783. .\}
  2784. .el \{\
  2785. .sp -1
  2786. .IP \(bu 2.3
  2787. .\}
  2788. \fIexclude=<pattern>\fR: Do not consider tags matching the given
  2789. \fBglob\fR(\fB7\fR) pattern, excluding the "refs/tags/" prefix\&.
  2790. .RE
  2791. .RE
  2792. .PP
  2793. \fI%S\fR
  2794. .RS 4
  2795. ref name given on the command line by which the commit was reached (like
  2796. \fBgit\fR
  2797. \fBlog\fR
  2798. \fB\-\-source\fR), only works with
  2799. \fBgit\fR
  2800. \fBlog\fR
  2801. .RE
  2802. .PP
  2803. \fI%e\fR
  2804. .RS 4
  2805. encoding
  2806. .RE
  2807. .PP
  2808. \fI%s\fR
  2809. .RS 4
  2810. subject
  2811. .RE
  2812. .PP
  2813. \fI%f\fR
  2814. .RS 4
  2815. sanitized subject line, suitable for a filename
  2816. .RE
  2817. .PP
  2818. \fI%b\fR
  2819. .RS 4
  2820. body
  2821. .RE
  2822. .PP
  2823. \fI%B\fR
  2824. .RS 4
  2825. raw body (unwrapped subject and body)
  2826. .RE
  2827. .PP
  2828. \fI%GG\fR
  2829. .RS 4
  2830. raw verification message from GPG for a signed commit
  2831. .RE
  2832. .PP
  2833. \fI%G?\fR
  2834. .RS 4
  2835. show "G" for a good (valid) signature, "B" for a bad signature, "U" for a good signature with unknown validity, "X" for a good signature that has expired, "Y" for a good signature made by an expired key, "R" for a good signature made by a revoked key, "E" if the signature cannot be checked (e\&.g\&. missing key) and "N" for no signature
  2836. .RE
  2837. .PP
  2838. \fI%GS\fR
  2839. .RS 4
  2840. show the name of the signer for a signed commit
  2841. .RE
  2842. .PP
  2843. \fI%GK\fR
  2844. .RS 4
  2845. show the key used to sign a signed commit
  2846. .RE
  2847. .PP
  2848. \fI%GF\fR
  2849. .RS 4
  2850. show the fingerprint of the key used to sign a signed commit
  2851. .RE
  2852. .PP
  2853. \fI%GP\fR
  2854. .RS 4
  2855. show the fingerprint of the primary key whose subkey was used to sign a signed commit
  2856. .RE
  2857. .PP
  2858. \fI%GT\fR
  2859. .RS 4
  2860. show the trust level for the key used to sign a signed commit
  2861. .RE
  2862. .PP
  2863. \fI%gD\fR
  2864. .RS 4
  2865. reflog selector, e\&.g\&.,
  2866. \fBrefs/stash@\fR{1} or
  2867. \fBrefs/stash@\fR{2
  2868. \fBminutes\fR
  2869. \fBago\fR}; the format follows the rules described for the
  2870. \fB\-g\fR
  2871. option\&. The portion before the
  2872. \fB@\fR
  2873. is the refname as given on the command line (so
  2874. \fBgit\fR
  2875. \fBlog\fR
  2876. \fB\-g\fR
  2877. \fBrefs/heads/master\fR
  2878. would yield
  2879. \fBrefs/heads/master@\fR{0})\&.
  2880. .RE
  2881. .PP
  2882. \fI%gd\fR
  2883. .RS 4
  2884. shortened reflog selector; same as %gD, but the refname portion is shortened for human readability (so
  2885. \fBrefs/heads/master\fR
  2886. becomes just
  2887. \fBmaster\fR)\&.
  2888. .RE
  2889. .PP
  2890. \fI%gn\fR
  2891. .RS 4
  2892. reflog identity name
  2893. .RE
  2894. .PP
  2895. \fI%gN\fR
  2896. .RS 4
  2897. reflog identity name (respecting \&.mailmap, see
  2898. \fBgit-shortlog\fR(1)
  2899. or
  2900. \fBgit-blame\fR(1))
  2901. .RE
  2902. .PP
  2903. \fI%ge\fR
  2904. .RS 4
  2905. reflog identity email
  2906. .RE
  2907. .PP
  2908. \fI%gE\fR
  2909. .RS 4
  2910. reflog identity email (respecting \&.mailmap, see
  2911. \fBgit-shortlog\fR(1)
  2912. or
  2913. \fBgit-blame\fR(1))
  2914. .RE
  2915. .PP
  2916. \fI%gs\fR
  2917. .RS 4
  2918. reflog subject
  2919. .RE
  2920. .PP
  2921. \fI%(trailers[:<options>])\fR
  2922. .RS 4
  2923. display the trailers of the body as interpreted by
  2924. \fBgit-interpret-trailers\fR(1)\&. The
  2925. \fBtrailers\fR
  2926. string may be followed by a colon and zero or more comma\-separated options\&. If any option is provided multiple times, the last occurrence wins\&.
  2927. .sp
  2928. .RS 4
  2929. .ie n \{\
  2930. \h'-04'\(bu\h'+03'\c
  2931. .\}
  2932. .el \{\
  2933. .sp -1
  2934. .IP \(bu 2.3
  2935. .\}
  2936. \fIkey=<key>\fR: only show trailers with specified <key>\&. Matching is done case\-insensitively and trailing colon is optional\&. If option is given multiple times trailer lines matching any of the keys are shown\&. This option automatically enables the
  2937. \fBonly\fR
  2938. option so that non\-trailer lines in the trailer block are hidden\&. If that is not desired it can be disabled with
  2939. \fBonly=false\fR\&. E\&.g\&., %(\fBtrailers:key=Reviewed\-by\fR) shows trailer lines with key
  2940. \fBReviewed\-by\fR\&.
  2941. .RE
  2942. .sp
  2943. .RS 4
  2944. .ie n \{\
  2945. \h'-04'\(bu\h'+03'\c
  2946. .\}
  2947. .el \{\
  2948. .sp -1
  2949. .IP \(bu 2.3
  2950. .\}
  2951. \fIonly[=<bool>]\fR: select whether non\-trailer lines from the trailer block should be included\&.
  2952. .RE
  2953. .sp
  2954. .RS 4
  2955. .ie n \{\
  2956. \h'-04'\(bu\h'+03'\c
  2957. .\}
  2958. .el \{\
  2959. .sp -1
  2960. .IP \(bu 2.3
  2961. .\}
  2962. \fIseparator=<sep>\fR: specify the separator inserted between trailer lines\&. Defaults to a line feed character\&. The string <sep> may contain the literal formatting codes described above\&. To use comma as separator one must use %x2C as it would otherwise be parsed as next option\&. E\&.g\&., %(\fBtrailers:key=Ticket,separator=\fR%x2C ) shows all trailer lines whose key is "Ticket" separated by a comma and a space\&.
  2963. .RE
  2964. .sp
  2965. .RS 4
  2966. .ie n \{\
  2967. \h'-04'\(bu\h'+03'\c
  2968. .\}
  2969. .el \{\
  2970. .sp -1
  2971. .IP \(bu 2.3
  2972. .\}
  2973. \fIunfold[=<bool>]\fR: make it behave as if interpret\-trailer\(cqs
  2974. \fB\-\-unfold\fR
  2975. option was given\&. E\&.g\&., %(\fBtrailers:only,unfold=true\fR) unfolds and shows all trailer lines\&.
  2976. .RE
  2977. .sp
  2978. .RS 4
  2979. .ie n \{\
  2980. \h'-04'\(bu\h'+03'\c
  2981. .\}
  2982. .el \{\
  2983. .sp -1
  2984. .IP \(bu 2.3
  2985. .\}
  2986. \fIkeyonly[=<bool>]\fR: only show the key part of the trailer\&.
  2987. .RE
  2988. .sp
  2989. .RS 4
  2990. .ie n \{\
  2991. \h'-04'\(bu\h'+03'\c
  2992. .\}
  2993. .el \{\
  2994. .sp -1
  2995. .IP \(bu 2.3
  2996. .\}
  2997. \fIvalueonly[=<bool>]\fR: only show the value part of the trailer\&.
  2998. .RE
  2999. .sp
  3000. .RS 4
  3001. .ie n \{\
  3002. \h'-04'\(bu\h'+03'\c
  3003. .\}
  3004. .el \{\
  3005. .sp -1
  3006. .IP \(bu 2.3
  3007. .\}
  3008. \fIkey_value_separator=<sep>\fR: specify the separator inserted between the key and value of each trailer\&. Defaults to ": "\&. Otherwise it shares the same semantics as
  3009. \fIseparator=<sep>\fR
  3010. above\&.
  3011. .RE
  3012. .RE
  3013. .RE
  3014. .if n \{\
  3015. .sp
  3016. .\}
  3017. .RS 4
  3018. .it 1 an-trap
  3019. .nr an-no-space-flag 1
  3020. .nr an-break-flag 1
  3021. .br
  3022. .ps +1
  3023. \fBNote\fR
  3024. .ps -1
  3025. .br
  3026. .sp
  3027. Some placeholders may depend on other options given to the revision traversal engine\&. For example, the %g* reflog options will insert an empty string unless we are traversing reflog entries (e\&.g\&., by \fBgit\fR \fBlog\fR \fB\-g\fR)\&. The %d and %D placeholders will use the "short" decoration format if \fB\-\-decorate\fR was not already provided on the command line\&.
  3028. .sp .5v
  3029. .RE
  3030. .sp
  3031. The boolean options accept an optional value [\fB=\fR\fI<bool\-value>\fR]\&. The values taken by \fB\-\-type=bool\fR git\-config[1], like \fByes\fR and \fBoff\fR, are all accepted\&. Giving a boolean option without \fB=\fR\fI<value>\fR is equivalent to giving it with \fB=true\fR\&.
  3032. .sp
  3033. If you add a \fB+\fR (plus sign) after \fI%\fR of a placeholder, a line\-feed is inserted immediately before the expansion if and only if the placeholder expands to a non\-empty string\&.
  3034. .sp
  3035. If you add a \fB\-\fR (minus sign) after \fI%\fR of a placeholder, all consecutive line\-feeds immediately preceding the expansion are deleted if and only if the placeholder expands to an empty string\&.
  3036. .sp
  3037. If you add a ` ` (space) after \fI%\fR of a placeholder, a space is inserted immediately before the expansion if and only if the placeholder expands to a non\-empty string\&.
  3038. .sp
  3039. .RS 4
  3040. .ie n \{\
  3041. \h'-04'\(bu\h'+03'\c
  3042. .\}
  3043. .el \{\
  3044. .sp -1
  3045. .IP \(bu 2.3
  3046. .\}
  3047. \fItformat:\fR
  3048. .sp
  3049. The
  3050. \fItformat:\fR
  3051. format works exactly like
  3052. \fIformat:\fR, except that it provides "terminator" semantics instead of "separator" semantics\&. In other words, each commit has the message terminator character (usually a newline) appended, rather than a separator placed between entries\&. This means that the final entry of a single\-line format will be properly terminated with a new line, just as the "oneline" format does\&. For example:
  3053. .sp
  3054. .if n \{\
  3055. .RS 4
  3056. .\}
  3057. .nf
  3058. $ git log \-2 \-\-pretty=format:%h 4da45bef \e
  3059.   | perl \-pe \*(Aq$_ \&.= " \-\- NO NEWLINE\en" unless /\en/\*(Aq
  3060. 4da45be
  3061. 7134973 \-\- NO NEWLINE
  3063. $ git log \-2 \-\-pretty=tformat:%h 4da45bef \e
  3064.   | perl \-pe \*(Aq$_ \&.= " \-\- NO NEWLINE\en" unless /\en/\*(Aq
  3065. 4da45be
  3066. 7134973
  3067. .fi
  3068. .if n \{\
  3069. .RE
  3070. .\}
  3071. .sp
  3072. In addition, any unrecognized string that has a % in it is interpreted as if it has
  3073. \fBtformat:\fR
  3074. in front of it\&. For example, these two are equivalent:
  3075. .sp
  3076. .if n \{\
  3077. .RS 4
  3078. .\}
  3079. .nf
  3080. $ git log \-2 \-\-pretty=tformat:%h 4da45bef
  3081. $ git log \-2 \-\-pretty=%h 4da45bef
  3082. .fi
  3083. .if n \{\
  3084. .RE
  3085. .\}
  3086. .RE
  3087. .SH "EXAMPLES"
  3088. .sp
  3089. .RS 4
  3090. .ie n \{\
  3091. \h'-04'\(bu\h'+03'\c
  3092. .\}
  3093. .el \{\
  3094. .sp -1
  3095. .IP \(bu 2.3
  3096. .\}
  3097. Print the list of commits reachable from the current branch\&.
  3098. .sp
  3099. .if n \{\
  3100. .RS 4
  3101. .\}
  3102. .nf
  3103. git rev\-list HEAD
  3104. .fi
  3105. .if n \{\
  3106. .RE
  3107. .\}
  3108. .RE
  3109. .sp
  3110. .RS 4
  3111. .ie n \{\
  3112. \h'-04'\(bu\h'+03'\c
  3113. .\}
  3114. .el \{\
  3115. .sp -1
  3116. .IP \(bu 2.3
  3117. .\}
  3118. Print the list of commits on this branch, but not present in the upstream branch\&.
  3119. .sp
  3120. .if n \{\
  3121. .RS 4
  3122. .\}
  3123. .nf
  3124. git rev\-list @{upstream}\&.\&.HEAD
  3125. .fi
  3126. .if n \{\
  3127. .RE
  3128. .\}
  3129. .RE
  3130. .sp
  3131. .RS 4
  3132. .ie n \{\
  3133. \h'-04'\(bu\h'+03'\c
  3134. .\}
  3135. .el \{\
  3136. .sp -1
  3137. .IP \(bu 2.3
  3138. .\}
  3139. Format commits with their author and commit message (see also the porcelain
  3140. \fBgit-log\fR(1))\&.
  3141. .sp
  3142. .if n \{\
  3143. .RS 4
  3144. .\}
  3145. .nf
  3146. git rev\-list \-\-format=medium HEAD
  3147. .fi
  3148. .if n \{\
  3149. .RE
  3150. .\}
  3151. .RE
  3152. .sp
  3153. .RS 4
  3154. .ie n \{\
  3155. \h'-04'\(bu\h'+03'\c
  3156. .\}
  3157. .el \{\
  3158. .sp -1
  3159. .IP \(bu 2.3
  3160. .\}
  3161. Format commits along with their diffs (see also the porcelain
  3162. \fBgit-log\fR(1), which can do this in a single process)\&.
  3163. .sp
  3164. .if n \{\
  3165. .RS 4
  3166. .\}
  3167. .nf
  3168. git rev\-list HEAD |
  3169. git diff\-tree \-\-stdin \-\-format=medium \-p
  3170. .fi
  3171. .if n \{\
  3172. .RE
  3173. .\}
  3174. .RE
  3175. .sp
  3176. .RS 4
  3177. .ie n \{\
  3178. \h'-04'\(bu\h'+03'\c
  3179. .\}
  3180. .el \{\
  3181. .sp -1
  3182. .IP \(bu 2.3
  3183. .\}
  3184. Print the list of commits on the current branch that touched any file in the
  3185. \fBDocumentation\fR
  3186. directory\&.
  3187. .sp
  3188. .if n \{\
  3189. .RS 4
  3190. .\}
  3191. .nf
  3192. git rev\-list HEAD \-\- Documentation/
  3193. .fi
  3194. .if n \{\
  3195. .RE
  3196. .\}
  3197. .RE
  3198. .sp
  3199. .RS 4
  3200. .ie n \{\
  3201. \h'-04'\(bu\h'+03'\c
  3202. .\}
  3203. .el \{\
  3204. .sp -1
  3205. .IP \(bu 2.3
  3206. .\}
  3207. Print the list of commits authored by you in the past year, on any branch, tag, or other ref\&.
  3208. .sp
  3209. .if n \{\
  3210. .RS 4
  3211. .\}
  3212. .nf
  3213. git rev\-list \-\-author=you@example\&.com \-\-since=1\&.year\&.ago \-\-all
  3214. .fi
  3215. .if n \{\
  3216. .RE
  3217. .\}
  3218. .RE
  3219. .sp
  3220. .RS 4
  3221. .ie n \{\
  3222. \h'-04'\(bu\h'+03'\c
  3223. .\}
  3224. .el \{\
  3225. .sp -1
  3226. .IP \(bu 2.3
  3227. .\}
  3228. Print the list of objects reachable from the current branch (i\&.e\&., all commits and the blobs and trees they contain)\&.
  3229. .sp
  3230. .if n \{\
  3231. .RS 4
  3232. .\}
  3233. .nf
  3234. git rev\-list \-\-objects HEAD
  3235. .fi
  3236. .if n \{\
  3237. .RE
  3238. .\}
  3239. .RE
  3240. .sp
  3241. .RS 4
  3242. .ie n \{\
  3243. \h'-04'\(bu\h'+03'\c
  3244. .\}
  3245. .el \{\
  3246. .sp -1
  3247. .IP \(bu 2.3
  3248. .\}
  3249. Compare the disk size of all reachable objects, versus those reachable from reflogs, versus the total packed size\&. This can tell you whether running
  3250. \fBgit\fR
  3251. \fBrepack\fR
  3252. \fB\-ad\fR
  3253. might reduce the repository size (by dropping unreachable objects), and whether expiring reflogs might help\&.
  3254. .sp
  3255. .if n \{\
  3256. .RS 4
  3257. .\}
  3258. .nf
  3259. # reachable objects
  3260. git rev\-list \-\-disk\-usage \-\-objects \-\-all
  3261. # plus reflogs
  3262. git rev\-list \-\-disk\-usage \-\-objects \-\-all \-\-reflog
  3263. # total disk size used
  3264. du \-c \&.git/objects/pack/*\&.pack \&.git/objects/??/*
  3265. # alternative to du: add up "size" and "size\-pack" fields
  3266. git count\-objects \-v
  3267. .fi
  3268. .if n \{\
  3269. .RE
  3270. .\}
  3271. .RE
  3272. .sp
  3273. .RS 4
  3274. .ie n \{\
  3275. \h'-04'\(bu\h'+03'\c
  3276. .\}
  3277. .el \{\
  3278. .sp -1
  3279. .IP \(bu 2.3
  3280. .\}
  3281. Report the disk size of each branch, not including objects used by the current branch\&. This can find outliers that are contributing to a bloated repository size (e\&.g\&., because somebody accidentally committed large build artifacts)\&.
  3282. .sp
  3283. .if n \{\
  3284. .RS 4
  3285. .\}
  3286. .nf
  3287. git for\-each\-ref \-\-format=\*(Aq%(refname)\*(Aq |
  3288. while read branch
  3289. do
  3290.         size=$(git rev\-list \-\-disk\-usage \-\-objects HEAD\&.\&.$branch)
  3291.         echo "$size $branch"
  3292. done |
  3293. sort \-n
  3294. .fi
  3295. .if n \{\
  3296. .RE
  3297. .\}
  3298. .RE
  3299. .sp
  3300. .RS 4
  3301. .ie n \{\
  3302. \h'-04'\(bu\h'+03'\c
  3303. .\}
  3304. .el \{\
  3305. .sp -1
  3306. .IP \(bu 2.3
  3307. .\}
  3308. Compare the on\-disk size of branches in one group of refs, excluding another\&. If you co\-mingle objects from multiple remotes in a single repository, this can show which remotes are contributing to the repository size (taking the size of
  3309. \fBorigin\fR
  3310. as a baseline)\&.
  3311. .sp
  3312. .if n \{\
  3313. .RS 4
  3314. .\}
  3315. .nf
  3316. git rev\-list \-\-disk\-usage \-\-objects \-\-remotes=$suspect \-\-not \-\-remotes=origin
  3317. .fi
  3318. .if n \{\
  3319. .RE
  3320. .\}
  3321. .RE
  3322. .SH "GIT"
  3323. .sp
  3324. Part of the \fBgit\fR(1) suite