| blob | 3ce99e5c00b0b62bb9c38a67fe23606df2fc79ff |
5 <head>
10 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
12 /* Default font. */
13 body {
14 font-family: Georgia,serif;
15 }
17 /* Title font. */
18 h1, h2, h3, h4, h5, h6,
19 div.title, caption.title,
20 thead, p.table.header,
21 #toctitle,
22 #author, #revnumber, #revdate, #revremark,
23 #footer {
24 font-family: Arial,Helvetica,sans-serif;
25 }
27 body {
29 }
31 a {
32 color: blue;
33 text-decoration: underline;
34 }
35 a:visited {
36 color: fuchsia;
37 }
39 em {
40 font-style: italic;
41 color: navy;
42 }
44 strong {
45 font-weight: bold;
46 color: #083194;
47 }
49 h1, h2, h3, h4, h5, h6 {
50 color: #527bbd;
51 margin-top: 1.2em;
52 margin-bottom: 0.5em;
53 line-height: 1.3;
54 }
56 h1, h2, h3 {
57 border-bottom: 2px solid silver;
58 }
59 h2 {
60 padding-top: 0.5em;
61 }
62 h3 {
63 float: left;
64 }
65 h3 + * {
66 clear: left;
67 }
68 h5 {
69 font-size: 1.0em;
70 }
72 div.sectionbody {
73 margin-left: 0;
74 }
76 hr {
77 border: 1px solid silver;
78 }
80 p {
81 margin-top: 0.5em;
82 margin-bottom: 0.5em;
83 }
85 ul, ol, li > p {
86 margin-top: 0;
87 }
88 ul > li { color: #aaa; }
91 .monospaced, code, pre {
92 font-family: "Courier New", Courier, monospace;
93 font-size: inherit;
94 color: navy;
95 padding: 0;
96 margin: 0;
97 }
98 pre {
99 white-space: pre-wrap;
100 }
102 #author {
103 color: #527bbd;
104 font-weight: bold;
105 font-size: 1.1em;
106 }
107 #email {
108 }
109 #revnumber, #revdate, #revremark {
110 }
112 #footer {
113 font-size: small;
114 border-top: 2px solid silver;
115 padding-top: 0.5em;
116 margin-top: 4.0em;
117 }
118 #footer-text {
119 float: left;
120 padding-bottom: 0.5em;
121 }
122 #footer-badges {
123 float: right;
124 padding-bottom: 0.5em;
125 }
127 #preamble {
128 margin-top: 1.5em;
129 margin-bottom: 1.5em;
130 }
131 div.imageblock, div.exampleblock, div.verseblock,
132 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
133 div.admonitionblock {
134 margin-top: 1.0em;
135 margin-bottom: 1.5em;
136 }
137 div.admonitionblock {
138 margin-top: 2.0em;
139 margin-bottom: 2.0em;
140 margin-right: 10%;
141 color: #606060;
142 }
144 div.content { /* Block element content. */
145 padding: 0;
146 }
148 /* Block element titles. */
149 div.title, caption.title {
150 color: #527bbd;
151 font-weight: bold;
152 text-align: left;
153 margin-top: 1.0em;
154 margin-bottom: 0.5em;
155 }
156 div.title + * {
157 margin-top: 0;
158 }
160 td div.title:first-child {
161 margin-top: 0.0em;
162 }
163 div.content div.title:first-child {
164 margin-top: 0.0em;
165 }
166 div.content + div.title {
167 margin-top: 0.0em;
168 }
170 div.sidebarblock > div.content {
171 background: #ffffee;
172 border: 1px solid #dddddd;
173 border-left: 4px solid #f0f0f0;
174 padding: 0.5em;
175 }
177 div.listingblock > div.content {
178 border: 1px solid #dddddd;
179 border-left: 5px solid #f0f0f0;
180 background: #f8f8f8;
181 padding: 0.5em;
182 }
184 div.quoteblock, div.verseblock {
185 padding-left: 1.0em;
186 margin-left: 1.0em;
187 margin-right: 10%;
188 border-left: 5px solid #f0f0f0;
189 color: #888;
190 }
192 div.quoteblock > div.attribution {
193 padding-top: 0.5em;
194 text-align: right;
195 }
197 div.verseblock > pre.content {
198 font-family: inherit;
199 font-size: inherit;
200 }
201 div.verseblock > div.attribution {
202 padding-top: 0.75em;
203 text-align: left;
204 }
205 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
206 div.verseblock + div.attribution {
207 text-align: left;
208 }
210 div.admonitionblock .icon {
211 vertical-align: top;
212 font-size: 1.1em;
213 font-weight: bold;
214 text-decoration: underline;
215 color: #527bbd;
216 padding-right: 0.5em;
217 }
218 div.admonitionblock td.content {
219 padding-left: 0.5em;
220 border-left: 3px solid #dddddd;
221 }
223 div.exampleblock > div.content {
224 border-left: 3px solid #dddddd;
225 padding-left: 0.5em;
226 }
228 div.imageblock div.content { padding-left: 0; }
229 span.image img { border-style: none; vertical-align: text-bottom; }
230 a.image:visited { color: white; }
232 dl {
233 margin-top: 0.8em;
234 margin-bottom: 0.8em;
235 }
236 dt {
237 margin-top: 0.5em;
238 margin-bottom: 0;
239 font-style: normal;
240 color: navy;
241 }
242 dd > *:first-child {
243 margin-top: 0.1em;
244 }
246 ul, ol {
247 list-style-position: outside;
248 }
249 ol.arabic {
250 list-style-type: decimal;
251 }
252 ol.loweralpha {
253 list-style-type: lower-alpha;
254 }
255 ol.upperalpha {
256 list-style-type: upper-alpha;
257 }
258 ol.lowerroman {
259 list-style-type: lower-roman;
260 }
261 ol.upperroman {
262 list-style-type: upper-roman;
263 }
265 div.compact ul, div.compact ol,
266 div.compact p, div.compact p,
267 div.compact div, div.compact div {
268 margin-top: 0.1em;
269 margin-bottom: 0.1em;
270 }
272 tfoot {
273 font-weight: bold;
274 }
275 td > div.verse {
276 white-space: pre;
277 }
279 div.hdlist {
280 margin-top: 0.8em;
281 margin-bottom: 0.8em;
282 }
283 div.hdlist tr {
284 padding-bottom: 15px;
285 }
286 dt.hdlist1.strong, td.hdlist1.strong {
287 font-weight: bold;
288 }
289 td.hdlist1 {
290 vertical-align: top;
291 font-style: normal;
292 padding-right: 0.8em;
293 color: navy;
294 }
295 td.hdlist2 {
296 vertical-align: top;
297 }
298 div.hdlist.compact tr {
299 margin: 0;
300 padding-bottom: 0;
301 }
303 .comment {
304 background: yellow;
305 }
307 .footnote, .footnoteref {
308 font-size: 0.8em;
309 }
311 span.footnote, span.footnoteref {
312 vertical-align: super;
313 }
315 #footnotes {
318 }
320 #footnotes div.footnote {
322 }
324 #footnotes hr {
325 border: none;
326 border-top: 1px solid silver;
327 height: 1px;
328 text-align: left;
329 margin-left: 0;
330 width: 20%;
331 min-width: 100px;
332 }
334 div.colist td {
335 padding-right: 0.5em;
336 padding-bottom: 0.3em;
337 vertical-align: top;
338 }
339 div.colist td img {
340 margin-top: 0.3em;
341 }
343 @media print {
344 #footer-badges { display: none; }
345 }
347 #toc {
348 margin-bottom: 2.5em;
349 }
351 #toctitle {
352 color: #527bbd;
353 font-size: 1.1em;
354 font-weight: bold;
355 margin-top: 1.0em;
356 margin-bottom: 0.1em;
357 }
359 div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
360 margin-top: 0;
361 margin-bottom: 0;
362 }
363 div.toclevel2 {
364 margin-left: 2em;
365 font-size: 0.9em;
366 }
367 div.toclevel3 {
368 margin-left: 4em;
369 font-size: 0.9em;
370 }
371 div.toclevel4 {
372 margin-left: 6em;
373 font-size: 0.9em;
374 }
376 span.aqua { color: aqua; }
377 span.black { color: black; }
378 span.blue { color: blue; }
379 span.fuchsia { color: fuchsia; }
380 span.gray { color: gray; }
381 span.green { color: green; }
382 span.lime { color: lime; }
383 span.maroon { color: maroon; }
384 span.navy { color: navy; }
385 span.olive { color: olive; }
386 span.purple { color: purple; }
387 span.red { color: red; }
388 span.silver { color: silver; }
389 span.teal { color: teal; }
390 span.white { color: white; }
391 span.yellow { color: yellow; }
393 span.aqua-background { background: aqua; }
394 span.black-background { background: black; }
395 span.blue-background { background: blue; }
396 span.fuchsia-background { background: fuchsia; }
397 span.gray-background { background: gray; }
398 span.green-background { background: green; }
399 span.lime-background { background: lime; }
400 span.maroon-background { background: maroon; }
401 span.navy-background { background: navy; }
402 span.olive-background { background: olive; }
403 span.purple-background { background: purple; }
404 span.red-background { background: red; }
405 span.silver-background { background: silver; }
406 span.teal-background { background: teal; }
407 span.white-background { background: white; }
408 span.yellow-background { background: yellow; }
410 span.big { font-size: 2em; }
411 span.small { font-size: 0.6em; }
413 span.underline { text-decoration: underline; }
414 span.overline { text-decoration: overline; }
415 span.line-through { text-decoration: line-through; }
417 div.unbreakable { page-break-inside: avoid; }
420 /*
421 * xhtml11 specific
422 *
423 * */
425 div.tableblock {
426 margin-top: 1.0em;
427 margin-bottom: 1.5em;
428 }
429 div.tableblock > table {
431 }
432 thead, p.table.header {
433 font-weight: bold;
434 color: #527bbd;
435 }
436 p.table {
437 margin-top: 0;
438 }
439 /* Because the table frame attribute is overridden by CSS in most browsers. */
441 border-style: none;
442 }
444 border-left-style: none;
445 border-right-style: none;
446 }
448 border-top-style: none;
449 border-bottom-style: none;
450 }
453 /*
454 * html5 specific
455 *
456 * */
458 table.tableblock {
459 margin-top: 1.0em;
460 margin-bottom: 1.5em;
461 }
462 thead, p.tableblock.header {
463 font-weight: bold;
464 color: #527bbd;
465 }
466 p.tableblock {
467 margin-top: 0;
468 }
469 table.tableblock {
470 border-width: 3px;
471 border-spacing: 0px;
472 border-style: solid;
473 border-color: #527bbd;
474 border-collapse: collapse;
475 }
476 th.tableblock, td.tableblock {
477 border-width: 1px;
478 padding: 4px;
479 border-style: solid;
480 border-color: #527bbd;
481 }
483 table.tableblock.frame-topbot {
484 border-left-style: hidden;
485 border-right-style: hidden;
486 }
487 table.tableblock.frame-sides {
488 border-top-style: hidden;
489 border-bottom-style: hidden;
490 }
491 table.tableblock.frame-none {
492 border-style: hidden;
493 }
495 th.tableblock.halign-left, td.tableblock.halign-left {
496 text-align: left;
497 }
498 th.tableblock.halign-center, td.tableblock.halign-center {
499 text-align: center;
500 }
501 th.tableblock.halign-right, td.tableblock.halign-right {
502 text-align: right;
503 }
505 th.tableblock.valign-top, td.tableblock.valign-top {
506 vertical-align: top;
507 }
508 th.tableblock.valign-middle, td.tableblock.valign-middle {
509 vertical-align: middle;
510 }
511 th.tableblock.valign-bottom, td.tableblock.valign-bottom {
512 vertical-align: bottom;
513 }
516 /*
517 * manpage specific
518 *
519 * */
521 body.manpage h1 {
522 padding-top: 0.5em;
523 padding-bottom: 0.5em;
524 border-top: 2px solid silver;
525 border-bottom: 2px solid silver;
526 }
527 body.manpage h2 {
528 border-style: none;
529 }
530 body.manpage div.sectionbody {
531 margin-left: 3em;
532 }
534 @media print {
535 body.manpage div#toc { display: none; }
536 }
539 </style>
541 /*<![CDATA[*/
542 var asciidoc = { // Namespace.
544 /////////////////////////////////////////////////////////////////////
545 // Table Of Contents generator
546 /////////////////////////////////////////////////////////////////////
548 /* Author: Mihai Bazon, September 2002
549 * http://students.infoiasi.ro/~mishoo
550 *
551 * Table Of Content generator
552 * Version: 0.4
553 *
554 * Feel free to use this script under the terms of the GNU General Public
555 * License, as long as you do not remove or alter this notice.
556 */
558 /* modified by Troy D. Hanson, September 2006. License: GPL */
562 toc: function (toclevels) {
564 function getText(el) {
565 var text = "";
566 for (var i = el.firstChild; i != null; i = i.nextSibling) {
567 if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
568 text += i.data;
569 else if (i.firstChild != null)
570 text += getText(i);
571 }
572 return text;
573 }
575 function TocEntry(el, text, toclevel) {
576 this.element = el;
577 this.text = text;
578 this.toclevel = toclevel;
579 }
581 function tocEntries(el, toclevels) {
582 var result = new Array;
584 // Function that scans the DOM tree for header elements (the DOM2
585 // nodeIterator API would be a better technique but not supported by all
586 // browsers).
587 var iterate = function (el) {
588 for (var i = el.firstChild; i != null; i = i.nextSibling) {
589 if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
590 var mo = re.exec(i.tagName);
593 }
594 iterate(i);
595 }
596 }
597 }
598 iterate(el);
599 return result;
600 }
602 var toc = document.getElementById("toc");
603 if (!toc) {
604 return;
605 }
607 // Delete existing TOC entries in case we're reloading the TOC.
608 var tocEntriesToRemove = [];
609 var i;
610 for (i = 0; i < toc.childNodes.length; i++) {
611 var entry = toc.childNodes[i];
612 if (entry.nodeName.toLowerCase() == 'div'
613 && entry.getAttribute("class")
614 && entry.getAttribute("class").match(/^toclevel/))
615 tocEntriesToRemove.push(entry);
616 }
617 for (i = 0; i < tocEntriesToRemove.length; i++) {
618 toc.removeChild(tocEntriesToRemove[i]);
619 }
621 // Rebuild TOC entries.
622 var entries = tocEntries(document.getElementById("content"), toclevels);
623 for (var i = 0; i < entries.length; ++i) {
624 var entry = entries[i];
625 if (entry.element.id == "")
626 entry.element.id = "_toc_" + i;
627 var a = document.createElement("a");
628 a.href = "#" + entry.element.id;
629 a.appendChild(document.createTextNode(entry.text));
630 var div = document.createElement("div");
631 div.appendChild(a);
632 div.className = "toclevel" + entry.toclevel;
633 toc.appendChild(div);
634 }
635 if (entries.length == 0)
636 toc.parentNode.removeChild(toc);
637 },
640 /////////////////////////////////////////////////////////////////////
641 // Footnotes generator
642 /////////////////////////////////////////////////////////////////////
644 /* Based on footnote generation code from:
646 */
648 footnotes: function () {
649 // Delete existing footnote entries in case we're reloading the footnodes.
650 var i;
651 var noteholder = document.getElementById("footnotes");
652 if (!noteholder) {
653 return;
654 }
655 var entriesToRemove = [];
656 for (i = 0; i < noteholder.childNodes.length; i++) {
657 var entry = noteholder.childNodes[i];
659 entriesToRemove.push(entry);
660 }
661 for (i = 0; i < entriesToRemove.length; i++) {
662 noteholder.removeChild(entriesToRemove[i]);
663 }
665 // Rebuild footnote entries.
666 var cont = document.getElementById("content");
667 var spans = cont.getElementsByTagName("span");
668 var refs = {};
669 var n = 0;
671 if (spans[i].className == "footnote") {
672 n++;
673 var note = spans[i].getAttribute("data-note");
674 if (!note) {
675 // Use [\s\S] in place of . so multi-line matches work.
676 // Because JavaScript has no s (dotall) regex flag.
677 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
678 spans[i].innerHTML =
681 spans[i].setAttribute("data-note", note);
682 }
683 noteholder.innerHTML +=
687 var id =spans[i].getAttribute("id");
688 if (id != null) refs["#"+id] = n;
689 }
690 }
691 if (n == 0)
692 noteholder.parentNode.removeChild(noteholder);
693 else {
694 // Process footnoterefs.
696 if (spans[i].className == "footnoteref") {
698 href = href.match(/#.*/)[0]; // Because IE return full URL.
699 n = refs[href];
700 spans[i].innerHTML =
701 "[<a href='#_footnote_" + n +
703 }
704 }
705 }
706 },
708 install: function(toclevels) {
709 var timerId;
711 function reinstall() {
712 asciidoc.footnotes();
713 if (toclevels) {
714 asciidoc.toc(toclevels);
715 }
716 }
718 function reinstallAndRemoveTimer() {
719 clearInterval(timerId);
720 reinstall();
721 }
723 timerId = setInterval(reinstall, 500);
724 if (document.addEventListener)
725 document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
726 else
727 window.onload = reinstallAndRemoveTimer;
728 }
730 }
731 asciidoc.install();
732 /*]]>*/
733 </script>
734 </head>
737 <h1>
738 git-rev-list(1) Manual Page
739 </h1>
742 <p>git-rev-list -
743 Lists commit objects in reverse chronological order
744 </p>
745 </div>
746 </div>
752 <pre class="content"><em>git rev-list</em> [<options>] <commit>… [--] [<path>…]</pre>
754 </div></div>
755 </div>
756 </div>
760 <div class="paragraph"><p>List commits that are reachable by following the <code>parent</code> links from the
761 given commit(s), but exclude commits that are reachable from the one(s)
763 chronological order by default.</p></div>
764 <div class="paragraph"><p>You can think of this as a set operation. Commits reachable from any of
765 the commits given on the command line form a set, and then commits reachable
767 set. The remaining commits are what comes out in the command’s output.
768 Various other options and paths parameters can be used to further limit the
769 result.</p></div>
774 </div></div>
775 <div class="paragraph"><p>means "list all the commits which are reachable from <em>foo</em> or <em>bar</em>, but
777 <div class="paragraph"><p>A special notation "<em><commit1></em>..<em><commit2></em>" can be used as a
778 short-hand for "^<em><commit1></em> <em><commit2></em>". For example, either of
779 the following may be used interchangeably:</p></div>
782 <pre><code>$ git rev-list origin..HEAD
783 $ git rev-list HEAD ^origin</code></pre>
784 </div></div>
785 <div class="paragraph"><p>Another special notation is "<em><commit1></em>…<em><commit2></em>" which is useful
786 for merges. The resulting set of commits is the symmetric difference
787 between the two operands. The following two commands are equivalent:</p></div>
790 <pre><code>$ git rev-list A B --not $(git merge-base --all A B)
791 $ git rev-list A...B</code></pre>
792 </div></div>
794 provides the ability to build and traverse commit ancestry graphs. For
795 this reason, it has a lot of different options that enables it to be
798 </div>
799 </div>
806 special notations explained in the description, additional commit
807 limiting may be applied.</p></div>
809 <code>--since=<date1></code> limits to commits newer than <code><date1></code>, and using it
817 </dt>
820 </dt>
823 </dt>
824 <dd>
825 <p>
826 Limit the number of commits to output.
827 </p>
828 </dd>
831 </dt>
832 <dd>
833 <p>
835 </p>
836 </dd>
839 </dt>
842 </dt>
843 <dd>
844 <p>
845 Show commits more recent than a specific date.
846 </p>
847 </dd>
850 </dt>
851 <dd>
852 <p>
853 Show all commits more recent than a specific date. This visits
854 all commits in the range, rather than stopping at the first commit which
855 is older than a specific date.
856 </p>
857 </dd>
860 </dt>
863 </dt>
864 <dd>
865 <p>
866 Show commits older than a specific date.
867 </p>
868 </dd>
871 </dt>
874 </dt>
875 <dd>
876 <p>
877 Limit the commits output to specified time range.
878 </p>
879 </dd>
882 </dt>
885 </dt>
886 <dd>
887 <p>
888 Limit the commits output to ones with author/committer
889 header lines that match the specified pattern (regular
891 commits whose author matches any of the given patterns are
893 </p>
894 </dd>
897 </dt>
898 <dd>
899 <p>
900 Limit the commits output to ones with reflog entries that
901 match the specified pattern (regular expression). With
903 matches any of the given patterns are chosen. It is an
905 </p>
906 </dd>
909 </dt>
910 <dd>
911 <p>
912 Limit the commits output to ones with log message that
913 matches the specified pattern (regular expression). With
915 matches any of the given patterns are chosen (but see
917 </p>
918 </dd>
920 --all-match
921 </dt>
922 <dd>
923 <p>
925 instead of ones that match at least one.
926 </p>
927 </dd>
929 --invert-grep
930 </dt>
931 <dd>
932 <p>
933 Limit the commits output to ones with log message that do not
935 </p>
936 </dd>
938 -i
939 </dt>
941 --regexp-ignore-case
942 </dt>
943 <dd>
944 <p>
945 Match the regular expression limiting patterns without regard to letter
946 case.
947 </p>
948 </dd>
950 --basic-regexp
951 </dt>
952 <dd>
953 <p>
954 Consider the limiting patterns to be basic regular expressions;
955 this is the default.
956 </p>
957 </dd>
959 -E
960 </dt>
962 --extended-regexp
963 </dt>
964 <dd>
965 <p>
966 Consider the limiting patterns to be extended regular expressions
967 instead of the default basic regular expressions.
968 </p>
969 </dd>
971 -F
972 </dt>
974 --fixed-strings
975 </dt>
976 <dd>
977 <p>
978 Consider the limiting patterns to be fixed strings (don’t interpret
979 pattern as a regular expression).
980 </p>
981 </dd>
983 -P
984 </dt>
986 --perl-regexp
987 </dt>
988 <dd>
989 <p>
990 Consider the limiting patterns to be Perl-compatible regular
991 expressions.
992 </p>
994 compile-time dependency. If Git wasn’t compiled with support for them
995 providing this option will cause it to die.</p></div>
996 </dd>
998 --remove-empty
999 </dt>
1000 <dd>
1001 <p>
1002 Stop when a given path disappears from the tree.
1003 </p>
1004 </dd>
1006 --merges
1007 </dt>
1008 <dd>
1009 <p>
1011 </p>
1012 </dd>
1014 --no-merges
1015 </dt>
1016 <dd>
1017 <p>
1018 Do not print commits with more than one parent. This is
1020 </p>
1021 </dd>
1024 </dt>
1027 </dt>
1029 --no-min-parents
1030 </dt>
1032 --no-max-parents
1033 </dt>
1034 <dd>
1035 <p>
1036 Show only commits which have at least (or at most) that many parent
1038 <code>--min-parents=2</code> is the same as <code>--merges</code>. <code>--max-parents=0</code>
1040 </p>
1041 <div class="paragraph"><p><code>--no-min-parents</code> and <code>--no-max-parents</code> reset these limits (to no limit)
1044 </dd>
1046 --first-parent
1047 </dt>
1048 <dd>
1049 <p>
1050 When finding commits to include, follow only the first
1051 parent commit upon seeing a merge commit. This option
1052 can give a better overview when viewing the evolution of
1053 a particular topic branch, because merges into a topic
1054 branch tend to be only about adjusting to updated upstream
1055 from time to time, and this option allows you to ignore
1056 the individual commits brought in to your history by such
1057 a merge.
1058 </p>
1059 </dd>
1061 --exclude-first-parent-only
1062 </dt>
1063 <dd>
1064 <p>
1066 the first parent commit upon seeing a merge commit.
1067 This can be used to find the set of changes in a topic branch
1068 from the point where it diverged from the remote branch, given
1069 that arbitrary merges can be valid topic branch changes.
1070 </p>
1071 </dd>
1073 --not
1074 </dt>
1075 <dd>
1076 <p>
1079 </p>
1080 </dd>
1082 --all
1083 </dt>
1084 <dd>
1085 <p>
1088 </p>
1089 </dd>
1092 </dt>
1093 <dd>
1094 <p>
1099 </p>
1100 </dd>
1103 </dt>
1104 <dd>
1105 <p>
1110 </p>
1111 </dd>
1114 </dt>
1115 <dd>
1116 <p>
1119 remote-tracking branches to ones matching given shell glob.
1120 If pattern lacks <em>?</em>, <em>*</em>, or <em>[</em>, <em>/*</em> at the end is implied.
1121 </p>
1122 </dd>
1125 </dt>
1126 <dd>
1127 <p>
1132 </p>
1133 </dd>
1136 </dt>
1137 <dd>
1138 <p>
1140 <code>--branches</code>, <code>--tags</code>, <code>--remotes</code>, or <code>--glob</code> would otherwise
1141 consider. Repetitions of this option accumulate exclusion patterns
1142 up to the next <code>--all</code>, <code>--branches</code>, <code>--tags</code>, <code>--remotes</code>, or
1144 accumulated patterns).
1145 </p>
1146 <div class="paragraph"><p>The patterns given should not begin with <code>refs/heads</code>, <code>refs/tags</code>, or
1147 <code>refs/remotes</code> when applied to <code>--branches</code>, <code>--tags</code>, or <code>--remotes</code>,
1150 explicitly.</p></div>
1151 </dd>
1153 --exclude-hidden=[fetch|receive|uploadpack]
1154 </dt>
1155 <dd>
1156 <p>
1163 </p>
1164 </dd>
1166 --reflog
1167 </dt>
1168 <dd>
1169 <p>
1170 Pretend as if all objects mentioned by reflogs are listed on the
1172 </p>
1173 </dd>
1175 --alternate-refs
1176 </dt>
1177 <dd>
1178 <p>
1179 Pretend as if all objects mentioned as ref tips of alternate
1180 repositories were listed on the command line. An alternate
1181 repository is any repository whose object directory is specified
1185 </p>
1186 </dd>
1188 --single-worktree
1189 </dt>
1190 <dd>
1191 <p>
1192 By default, all working trees will be examined by the
1193 following options when there are more than one (see
1194 <a href="git-worktree.html">git-worktree(1)</a>): <code>--all</code>, <code>--reflog</code> and
1196 This option forces them to examine the current working tree
1197 only.
1198 </p>
1199 </dd>
1201 --ignore-missing
1202 </dt>
1203 <dd>
1204 <p>
1205 Upon seeing an invalid object name in the input, pretend as if
1206 the bad input was not given.
1207 </p>
1208 </dd>
1210 --stdin
1211 </dt>
1212 <dd>
1213 <p>
1216 seen, stop reading commits and start reading paths to limit the
1217 result.
1218 </p>
1219 </dd>
1221 --quiet
1222 </dt>
1223 <dd>
1224 <p>
1225 Don’t print anything to standard output. This form
1226 is primarily meant to allow the caller to
1227 test the exit status to see if a range of objects is fully
1228 connected (or not). It is faster than redirecting stdout
1230 </p>
1231 </dd>
1233 --disk-usage
1234 </dt>
1236 --disk-usage=human
1237 </dt>
1238 <dd>
1239 <p>
1240 Suppress normal output; instead, print the sum of the bytes used
1241 for on-disk storage by the selected commits or objects. This is
1242 equivalent to piping the output into <code>git cat-file
1243 --batch-check='%(objectsize:disk)'</code>, except that it runs much
1246 "on-disk storage" means.
1249 </p>
1250 </dd>
1252 --cherry-mark
1253 </dt>
1254 <dd>
1255 <p>
1258 </p>
1259 </dd>
1261 --cherry-pick
1262 </dt>
1263 <dd>
1264 <p>
1265 Omit any commit that introduces the same change as
1267 commits are limited with symmetric difference.
1268 </p>
1269 <div class="paragraph"><p>For example, if you have two branches, <code>A</code> and <code>B</code>, a usual way
1270 to list all commits on only one side of them is with
1274 cherry-picked from branch A). With this option, such pairs of commits are
1275 excluded from the output.</p></div>
1276 </dd>
1278 --left-only
1279 </dt>
1281 --right-only
1282 </dt>
1283 <dd>
1284 <p>
1285 List only commits on the respective side of a symmetric difference,
1288 </p>
1289 <div class="paragraph"><p>For example, <code>--cherry-pick --right-only A...B</code> omits those
1291 <code>A</code>. In other words, this lists the <code>+</code> commits from <code>git cherry A B</code>.
1293 list.</p></div>
1294 </dd>
1296 --cherry
1297 </dt>
1298 <dd>
1299 <p>
1301 limit the output to the commits on our side and mark those that
1302 have been applied to the other side of a forked history with
1305 </p>
1306 </dd>
1308 -g
1309 </dt>
1311 --walk-reflogs
1312 </dt>
1313 <dd>
1314 <p>
1315 Instead of walking the commit ancestry chain, walk
1316 reflog entries from the most recent one to older ones.
1317 When this option is used you cannot specify commits to
1320 </p>
1321 <div class="paragraph"><p>With <code>--pretty</code> format other than <code>oneline</code> and <code>reference</code> (for obvious reasons),
1322 this causes the output to have two extra lines of information
1323 taken from the reflog. The reflog designator in the output may be shown
1326 depending on a few rules:</p></div>
1330 <li>
1331 <p>
1333 format.
1334 </p>
1335 </li>
1336 <li>
1337 <p>
1339 timestamp format.
1340 </p>
1341 </li>
1342 <li>
1343 <p>
1346 </p>
1347 </li>
1348 <li>
1349 <p>
1350 Otherwise, show the index format.
1351 </p>
1352 </li>
1353 </ol></div>
1354 </div></div>
1356 prefixed with this information on the same line.
1359 <div class="paragraph"><p>Under <code>--pretty=reference</code>, this information will not be shown at all.</p></div>
1360 </dd>
1362 --merge
1363 </dt>
1364 <dd>
1365 <p>
1366 After a failed merge, show refs that touch files having a
1367 conflict and don’t exist on all heads to merge.
1368 </p>
1369 </dd>
1371 --boundary
1372 </dt>
1373 <dd>
1374 <p>
1375 Output excluded boundary commits. Boundary commits are
1377 </p>
1378 </dd>
1380 --use-bitmap-index
1381 </dt>
1382 <dd>
1383 <p>
1384 Try to speed up the traversal using the pack bitmap index (if
1386 trees and blobs will not have their associated path printed.
1387 </p>
1388 </dd>
1391 </dt>
1392 <dd>
1393 <p>
1394 Show progress reports on stderr as objects are considered. The
1396 </p>
1397 </dd>
1398 </dl></div>
1399 </div>
1402 <div class="paragraph"><p>Sometimes you are only interested in parts of the history, for example the
1405 is how to do it, as there are various strategies to simplify the history.</p></div>
1410 </dt>
1411 <dd>
1412 <p>
1414 </p>
1415 </dd>
1417 --simplify-by-decoration
1418 </dt>
1419 <dd>
1420 <p>
1421 Commits that are referred by some branch or tag are selected.
1422 </p>
1423 </dd>
1424 </dl></div>
1425 <div class="paragraph"><p>Note that extra commits can be shown to give a meaningful history.</p></div>
1426 <div class="paragraph"><p>The following options affect the way the simplification is performed:</p></div>
1429 Default mode
1430 </dt>
1431 <dd>
1432 <p>
1433 Simplifies the history to the simplest history explaining the
1434 final state of the tree. Simplest because it prunes some side
1435 branches if the end result is the same (i.e. merging branches
1436 with the same content)
1437 </p>
1438 </dd>
1440 --show-pulls
1441 </dt>
1442 <dd>
1443 <p>
1444 Include all commits from the default mode, but also any merge
1445 commits that are not TREESAME to the first parent but are
1446 TREESAME to a later parent. This mode is helpful for showing
1447 the merge commits that "first introduced" a change to a branch.
1448 </p>
1449 </dd>
1451 --full-history
1452 </dt>
1453 <dd>
1454 <p>
1455 Same as the default mode, but does not prune some history.
1456 </p>
1457 </dd>
1459 --dense
1460 </dt>
1461 <dd>
1462 <p>
1463 Only the selected commits are shown, plus some to have a
1464 meaningful history.
1465 </p>
1466 </dd>
1468 --sparse
1469 </dt>
1470 <dd>
1471 <p>
1472 All commits in the simplified history are shown.
1473 </p>
1474 </dd>
1476 --simplify-merges
1477 </dt>
1478 <dd>
1479 <p>
1481 merges from the resulting history, as there are no selected
1482 commits contributing to this merge.
1483 </p>
1484 </dd>
1487 </dt>
1488 <dd>
1489 <p>
1495 times; if so, a commit is included if it is any of the commits
1496 given or if it is an ancestor or descendant of one of them.
1497 </p>
1498 </dd>
1499 </dl></div>
1501 <div class="paragraph"><p>Suppose you specified <code>foo</code> as the <paths>. We shall call commits
1504 <div class="paragraph"><p>In the following, we will always refer to the same example history to
1505 illustrate the differences between simplification settings. We assume
1509 <pre><code> .-A---M---N---O---P---Q
1510 / / / / / /
1511 I B C D E Y
1512 \ / / / / /
1513 `-------------' X</code></pre>
1514 </div></div>
1515 <div class="paragraph"><p>The horizontal line of history A---Q is taken to be the first parent of
1516 each merge. The commits are:</p></div>
1518 <li>
1519 <p>
1521 “asdf”, and a file <code>quux</code> exists with contents “quux”. Initial
1523 </p>
1524 </li>
1525 <li>
1526 <p>
1528 </p>
1529 </li>
1530 <li>
1531 <p>
1532 <code>B</code> contains the same change as <code>A</code>. Its merge <code>M</code> is trivial and
1533 hence TREESAME to all parents.
1534 </p>
1535 </li>
1536 <li>
1537 <p>
1538 <code>C</code> does not change <code>foo</code>, but its merge <code>N</code> changes it to “foobar”,
1539 so it is not TREESAME to any parent.
1540 </p>
1541 </li>
1542 <li>
1543 <p>
1544 <code>D</code> sets <code>foo</code> to “baz”. Its merge <code>O</code> combines the strings from
1545 <code>N</code> and <code>D</code> to “foobarbaz”; i.e., it is not TREESAME to any parent.
1546 </p>
1547 </li>
1548 <li>
1549 <p>
1550 <code>E</code> changes <code>quux</code> to “xyzzy”, and its merge <code>P</code> combines the
1551 strings to “quux xyzzy”. <code>P</code> is TREESAME to <code>O</code>, but not to <code>E</code>.
1552 </p>
1553 </li>
1554 <li>
1555 <p>
1556 <code>X</code> is an independent root commit that added a new file <code>side</code>, and <code>Y</code>
1557 modified it. <code>Y</code> is TREESAME to <code>X</code>. Its merge <code>Q</code> added <code>side</code> to <code>P</code>, and
1559 </p>
1560 </li>
1561 </ul></div>
1562 <div class="paragraph"><p><code>rev-list</code> walks backwards through history, including or excluding
1565 are available.</p></div>
1568 Default mode
1569 </dt>
1570 <dd>
1571 <p>
1572 Commits are included if they are not TREESAME to any parent
1574 commit was a merge, and it was TREESAME to one parent, follow
1575 only that parent. (Even if there are several TREESAME
1576 parents, follow only one of them.) Otherwise, follow all
1577 parents.
1578 </p>
1582 <pre><code> .-A---N---O
1583 / / /
1584 I---------D</code></pre>
1585 </div></div>
1590 <div class="paragraph"><p>Parent/child relations are only visible with <code>--parents</code>, but that does
1591 not affect the commits selected in default mode, so we have shown the
1592 parent lines.</p></div>
1593 </dd>
1595 --full-history without parent rewriting
1596 </dt>
1597 <dd>
1598 <p>
1599 This mode differs from the default in one point: always follow
1600 all parents of a merge, even if it is TREESAME to one of them.
1601 Even if more than one side of the merge has commits that are
1602 included, this does not imply that the merge itself is! In
1603 the example, we get
1604 </p>
1608 </div></div>
1609 <div class="paragraph"><p><code>M</code> was excluded because it is TREESAME to both parents. <code>E</code>,
1610 <code>C</code> and <code>B</code> were all walked, but only <code>B</code> was !TREESAME, so the others
1611 do not appear.</p></div>
1612 <div class="paragraph"><p>Note that without parent rewriting, it is not really possible to talk
1613 about the parent/child relationships between the commits, so we show
1614 them disconnected.</p></div>
1615 </dd>
1617 --full-history with parent rewriting
1618 </dt>
1619 <dd>
1620 <p>
1621 Ordinary commits are only included if they are !TREESAME
1623 </p>
1625 Along each parent, prune away commits that are not included
1626 themselves. This results in</p></div>
1629 <pre><code> .-A---M---N---O---P---Q
1630 / / / / /
1631 I B / D /
1632 \ / / / /
1633 `-------------'</code></pre>
1634 </div></div>
1635 <div class="paragraph"><p>Compare to <code>--full-history</code> without rewriting above. Note that <code>E</code>
1636 was pruned away because it is TREESAME, but the parent list of P was
1637 rewritten to contain <code>E</code>'s parent <code>I</code>. The same happened for <code>C</code> and
1639 </dd>
1640 </dl></div>
1642 affects inclusion:</p></div>
1645 --dense
1646 </dt>
1647 <dd>
1648 <p>
1649 Commits that are walked are included if they are not TREESAME
1650 to any parent.
1651 </p>
1652 </dd>
1654 --sparse
1655 </dt>
1656 <dd>
1657 <p>
1658 All commits that are walked are included.
1659 </p>
1660 <div class="paragraph"><p>Note that without <code>--full-history</code>, this still simplifies merges: if
1661 one of the parents is TREESAME, we follow only that one, so the other
1662 sides of the merge are never walked.</p></div>
1663 </dd>
1665 --simplify-merges
1666 </dt>
1667 <dd>
1668 <p>
1669 First, build a history graph in the same way that
1671 </p>
1672 <div class="paragraph"><p>Then simplify each commit <code>C</code> to its replacement <code>C'</code> in the final
1673 history according to the following rules:</p></div>
1677 <li>
1678 <p>
1680 </p>
1681 </li>
1682 <li>
1683 <p>
1684 Replace each parent <code>P</code> of <code>C'</code> with its simplification <code>P'</code>. In
1685 the process, drop parents that are ancestors of other parents or that are
1686 root commits TREESAME to an empty tree, and remove duplicates, but take care
1687 to never drop all parents that we are TREESAME to.
1688 </p>
1689 </li>
1690 <li>
1691 <p>
1694 Otherwise, it is replaced with its only parent.
1695 </p>
1696 </li>
1697 </ul></div>
1698 </div></div>
1703 <pre><code> .-A---M---N---O
1704 / / /
1705 I B D
1706 \ / /
1707 `---------'</code></pre>
1708 </div></div>
1709 <div class="paragraph"><p>Note the major differences in <code>N</code>, <code>P</code>, and <code>Q</code> over <code>--full-history</code>:</p></div>
1713 <li>
1714 <p>
1717 </p>
1718 </li>
1719 <li>
1720 <p>
1722 removed completely, because it had one parent and is TREESAME.
1723 </p>
1724 </li>
1725 <li>
1726 <p>
1727 <code>Q</code>'s parent list had <code>Y</code> simplified to <code>X</code>. <code>X</code> was then removed, because it
1729 parent and is TREESAME.
1730 </p>
1731 </li>
1732 </ul></div>
1733 </div></div>
1734 </dd>
1735 </dl></div>
1740 </dt>
1741 <dd>
1742 <p>
1743 Limit the displayed commits to those which are an ancestor of
1745 itself.
1746 </p>
1747 <div class="paragraph"><p>As an example use case, consider the following commit history:</p></div>
1750 <pre><code> D---E-------F
1751 / \ \
1752 B---C---G---H---I---J
1753 / \
1754 A-------K---------------L--M</code></pre>
1755 </div></div>
1756 <div class="paragraph"><p>A regular <em>D..M</em> computes the set of commits that are ancestors of <code>M</code>,
1759 that “what does <code>M</code> have that did not exist in <code>D</code>”. The result in this
1760 example would be all the commits, except <code>A</code> and <code>B</code> (and <code>D</code> itself,
1761 of course).</p></div>
1762 <div class="paragraph"><p>When we want to find out what commits in <code>M</code> are contaminated with the
1765 excluding <code>C</code> and <code>K</code>. This is exactly what the <code>--ancestry-path</code>
1769 <pre><code> E-------F
1770 \ \
1771 G---H---I---J
1772 \
1773 L--M</code></pre>
1774 </div></div>
1775 <div class="paragraph"><p>We can also use <code>--ancestry-path=D</code> instead of <code>--ancestry-path</code> which
1777 explicit.</p></div>
1778 <div class="paragraph"><p>If we instead are interested in a given topic within this range, and all
1779 commits affected by that topic, we may only want to view the subset of
1784 <pre><code> E
1785 \
1786 G---H---I---J
1787 \
1788 L--M</code></pre>
1789 </div></div>
1790 <div class="paragraph"><p>Whereas <code>--ancestry-path=K D..M</code> would result in</p></div>
1794 </div></div>
1795 </dd>
1796 </dl></div>
1797 <div class="paragraph"><p>Before discussing another option, <code>--show-pulls</code>, we need to
1798 create a new example history.</p></div>
1799 <div class="paragraph"><p>A common problem users face when looking at simplified history is that a
1800 commit they know changed a file somehow does not appear in the file’s
1801 simplified history. Let’s demonstrate a new example and show how options
1802 such as <code>--full-history</code> and <code>--simplify-merges</code> works in that case:</p></div>
1805 <pre><code> .-A---M-----C--N---O---P
1806 / / \ \ \/ / /
1807 I B \ R-'`-Z' /
1808 \ / \/ /
1809 \ / /\ /
1810 `---X--' `---Y--'</code></pre>
1811 </div></div>
1812 <div class="paragraph"><p>For this example, suppose <code>I</code> created <code>file.txt</code> which was modified by
1813 <code>A</code>, <code>B</code>, and <code>X</code> in different ways. The single-parent commits <code>C</code>, <code>Z</code>,
1814 and <code>Y</code> do not change <code>file.txt</code>. The merge commit <code>M</code> was created by
1818 the contents of <code>file.txt</code> at <code>X</code>. Hence, <code>R</code> is TREESAME to <code>X</code> but not
1820 contents of <code>file.txt</code> at <code>R</code>, so <code>N</code> is TREESAME to <code>R</code> but not <code>C</code>.
1823 <div class="paragraph"><p>When using the default mode, <code>N</code> and <code>R</code> both have a TREESAME parent, so
1824 those edges are walked and the others are ignored. The resulting history
1825 graph is:</p></div>
1829 </div></div>
1830 <div class="paragraph"><p>When using <code>--full-history</code>, Git walks every edge. This will discover
1831 the commits <code>A</code> and <code>B</code> and the merge <code>M</code>, but also will reveal the
1832 merge commits <code>O</code> and <code>P</code>. With parent rewriting, the resulting graph is:</p></div>
1835 <pre><code> .-A---M--------N---O---P
1836 / / \ \ \/ / /
1837 I B \ R-'`--' /
1838 \ / \/ /
1839 \ / /\ /
1840 `---X--' `------'</code></pre>
1841 </div></div>
1842 <div class="paragraph"><p>Here, the merge commits <code>O</code> and <code>P</code> contribute extra noise, as they did
1845 issue in repositories using a workflow where many contributors work in
1846 parallel and merge their topic branches along a single trunk: many
1848 <div class="paragraph"><p>When using the <code>--simplify-merges</code> option, the commits <code>O</code> and <code>P</code>
1849 disappear from the results. This is because the rewritten second parents
1851 removed and then the commits look like single-parent commits that are
1853 in a history view as follows:</p></div>
1856 <pre><code> .-A---M--.
1857 / / \
1858 I B R
1859 \ / /
1860 \ / /
1861 `---X--'</code></pre>
1862 </div></div>
1864 <code>A</code>, <code>B</code>, and <code>X</code>. We also see the carefully-resolved merge <code>M</code> and the
1867 the default view. However, there are a few issues with this approach.</p></div>
1870 before returning a single result. This can make the option difficult to
1871 use for very large repositories.</p></div>
1872 <div class="paragraph"><p>The second issue is one of auditing. When many contributors are working
1873 on the same repository, it is important which merge commits introduced
1875 not likely to be the merge commit that was used to merge into an
1876 important branch. Instead, the merge <code>N</code> was used to merge <code>R</code> and <code>X</code>
1877 into the important branch. This commit may have information about why
1878 the change <code>X</code> came to override the changes from <code>A</code> and <code>B</code> in its
1879 commit message.</p></div>
1882 --show-pulls
1883 </dt>
1884 <dd>
1885 <p>
1886 In addition to the commits shown in the default history, show
1887 each merge commit that is not TREESAME to its first parent but
1888 is TREESAME to a later parent.
1889 </p>
1890 <div class="paragraph"><p>When a merge commit is included by <code>--show-pulls</code>, the merge is
1891 treated as if it "pulled" the change from another branch. When using
1893 graph is:</p></div>
1897 </div></div>
1898 <div class="paragraph"><p>Here, the merge commits <code>R</code> and <code>N</code> are included because they pulled
1901 default history.</p></div>
1902 <div class="paragraph"><p>When <code>--show-pulls</code> is paired with <code>--simplify-merges</code>, the
1903 graph includes all of the necessary information:</p></div>
1906 <pre><code> .-A---M--. N
1907 / / \ /
1908 I B R
1909 \ / /
1910 \ / /
1911 `---X--'</code></pre>
1912 </div></div>
1913 <div class="paragraph"><p>Notice that since <code>M</code> is reachable from <code>R</code>, the edge from <code>N</code> to <code>M</code>
1916 branch.</p></div>
1917 </dd>
1918 </dl></div>
1919 <div class="paragraph"><p>The <code>--simplify-by-decoration</code> option allows you to view only the
1920 big picture of the topology of the history, by omitting commits
1921 that are not referenced by tags. Commits are marked as !TREESAME
1922 (in other words, kept after history simplification rules described
1924 contents of the paths given on the command line. All other
1925 commits are marked as TREESAME (subject to be simplified away).</p></div>
1926 </div>
1931 --bisect
1932 </dt>
1933 <dd>
1934 <p>
1935 Limit output to the one commit object which is roughly halfway between
1936 included and excluded commits. Note that the bad bisection ref
1939 added to the excluded commits (if they exist). Thus, supposing there
1941 </p>
1945 </div></div>
1949 <pre><code> $ git rev-list foo ^midpoint
1950 $ git rev-list midpoint ^bar ^baz</code></pre>
1951 </div></div>
1953 introduces a regression is thus reduced to a binary search: repeatedly
1954 generate and test new 'midpoint’s until the commit chain is of length
1955 one.</p></div>
1956 </dd>
1958 --bisect-vars
1959 </dt>
1960 <dd>
1961 <p>
1964 text ready to be eval’ed by the shell. These lines will assign the
1972 </p>
1973 </dd>
1975 --bisect-all
1976 </dt>
1977 <dd>
1978 <p>
1979 This outputs all the commit objects between the included and excluded
1980 commits, ordered by their distance to the included and excluded
1982 from them is displayed first. (This is the only one displayed by
1984 </p>
1986 test when you want to avoid to test some of them for some reason (they
1987 may not compile for example).</p></div>
1988 <div class="paragraph"><p>This option can be used along with <code>--bisect-vars</code>, in this case,
1989 after all the sorted commit objects, there will be the same text as if
1991 </dd>
1992 </dl></div>
1993 </div>
1996 <div class="paragraph"><p>By default, the commits are shown in reverse chronological order.</p></div>
1999 --date-order
2000 </dt>
2001 <dd>
2002 <p>
2003 Show no parents before all of its children are shown, but
2004 otherwise show commits in the commit timestamp order.
2005 </p>
2006 </dd>
2008 --author-date-order
2009 </dt>
2010 <dd>
2011 <p>
2012 Show no parents before all of its children are shown, but
2013 otherwise show commits in the author timestamp order.
2014 </p>
2015 </dd>
2017 --topo-order
2018 </dt>
2019 <dd>
2020 <p>
2021 Show no parents before all of its children are shown, and
2022 avoid showing commits on multiple lines of history
2023 intermixed.
2024 </p>
2029 \ \
2031 </div></div>
2035 <div class="paragraph"><p>With <code>--topo-order</code>, they would show 8 6 5 3 7 4 2 1 (or 8 7 4 2 6 5
2036 3 1); some older commits are shown before newer ones in order to
2037 avoid showing the commits from two parallel development track mixed
2038 together.</p></div>
2039 </dd>
2041 --reverse
2042 </dt>
2043 <dd>
2044 <p>
2045 Output the commits chosen to be shown (see Commit Limiting
2046 section above) in reverse order. Cannot be combined with
2048 </p>
2049 </dd>
2050 </dl></div>
2051 </div>
2054 <div class="paragraph"><p>These options are mostly targeted for packing of Git repositories.</p></div>
2057 --objects
2058 </dt>
2059 <dd>
2060 <p>
2061 Print the object IDs of any object referenced by the listed
2063 all object IDs which I need to download if I have the commit
2065 </p>
2066 </dd>
2068 --in-commit-order
2069 </dt>
2070 <dd>
2071 <p>
2072 Print tree and blob ids in order of the commits. The tree
2073 and blob ids are printed after they are first referenced
2074 by a commit.
2075 </p>
2076 </dd>
2078 --objects-edge
2079 </dt>
2080 <dd>
2081 <p>
2084 <a href="git-pack-objects.html">git-pack-objects(1)</a> to build a “thin” pack, which records
2085 objects in deltified form based on objects contained in these
2086 excluded commits to reduce network traffic.
2087 </p>
2088 </dd>
2090 --objects-edge-aggressive
2091 </dt>
2092 <dd>
2093 <p>
2095 commits at the cost of increased time. This is used instead of
2097 </p>
2098 </dd>
2100 --indexed-objects
2101 </dt>
2102 <dd>
2103 <p>
2104 Pretend as if all trees and blobs used by the index are listed
2105 on the command line. Note that you probably want to use
2107 </p>
2108 </dd>
2110 --unpacked
2111 </dt>
2112 <dd>
2113 <p>
2115 in packs.
2116 </p>
2117 </dd>
2119 --object-names
2120 </dt>
2121 <dd>
2122 <p>
2124 that are found. This is the default behavior.
2125 </p>
2126 </dd>
2128 --no-object-names
2129 </dt>
2130 <dd>
2131 <p>
2134 the output to be more easily parsed by commands such as
2136 </p>
2137 </dd>
2140 </dt>
2141 <dd>
2142 <p>
2145 may be one of the following:
2146 </p>
2148 <div class="paragraph"><p>The form <em>--filter=blob:limit=<n>[kmg]</em> omits blobs larger than n bytes
2149 or units. n may be zero. The suffixes k, m, and g can be used to name
2152 <div class="paragraph"><p>The form <em>--filter=object:type=(tag|commit|tree|blob)</em> omits all objects
2153 which are not of the requested type.</p></div>
2154 <div class="paragraph"><p>The form <em>--filter=sparse:oid=<blob-ish></em> uses a sparse-checkout
2156 to omit blobs that would not be required for a sparse checkout on
2157 the requested refs.</p></div>
2158 <div class="paragraph"><p>The form <em>--filter=tree:<depth></em> omits all blobs and trees whose depth
2161 any trees or blobs unless included explicitly in the command-line (or
2163 tree and blobs which are referenced directly by a commit reachable from
2165 while also including trees and blobs one more level removed from an
2166 explicitly-given commit or tree.</p></div>
2167 <div class="paragraph"><p>Note that the form <em>--filter=sparse:path=<path></em> that wants to read
2168 from an arbitrary path on the filesystem has been dropped for security
2169 reasons.</p></div>
2170 <div class="paragraph"><p>Multiple <em>--filter=</em> flags can be specified to combine filters. Only
2171 objects which are accepted by every filter are included.</p></div>
2172 <div class="paragraph"><p>The form <em>--filter=combine:<filter1>+<filter2>+…<filterN></em> can also be
2173 used to combined several filters, but this is harder than just repeating
2177 reserved and also must be encoded: <code>~!@#$^&*()[]{}\;",<>?</code><code>'`</code>
2178 as well as all characters with ASCII code <= <code>0x20</code>, which includes
2179 space and newline.</p></div>
2181 <em>combine:tree:3+blob:none</em> and <em>combine:tree%3A3+blob%3Anone</em> are
2182 equivalent.</p></div>
2183 </dd>
2185 --no-filter
2186 </dt>
2187 <dd>
2188 <p>
2189 Turn off any previous <code>--filter=</code> argument.
2190 </p>
2191 </dd>
2193 --filter-provided-objects
2194 </dt>
2195 <dd>
2196 <p>
2197 Filter the list of explicitly provided objects, which would otherwise
2198 always be printed even if they did not match any of the filters. Only
2199 useful with <code>--filter=</code>.
2200 </p>
2201 </dd>
2203 --filter-print-omitted
2204 </dt>
2205 <dd>
2206 <p>
2207 Only useful with <code>--filter=</code>; prints a list of the objects omitted
2208 by the filter. Object IDs are prefixed with a “~” character.
2209 </p>
2210 </dd>
2212 --missing=<missing-action>
2213 </dt>
2214 <dd>
2215 <p>
2217 This option specifies how missing objects are handled.
2218 </p>
2219 <div class="paragraph"><p>The form <em>--missing=error</em> requests that rev-list stop with an error if
2220 a missing object is encountered. This is the default action.</p></div>
2221 <div class="paragraph"><p>The form <em>--missing=allow-any</em> will allow object traversal to continue
2222 if a missing object is encountered. Missing objects will silently be
2223 omitted from the results.</p></div>
2224 <div class="paragraph"><p>The form <em>--missing=allow-promisor</em> is like <em>allow-any</em>, but will only
2225 allow object traversal to continue for EXPECTED promisor missing objects.
2226 Unexpected missing objects will raise an error.</p></div>
2227 <div class="paragraph"><p>The form <em>--missing=print</em> is like <em>allow-any</em>, but will also print a
2228 list of the missing objects. Object IDs are prefixed with a “?” character.</p></div>
2229 </dd>
2231 --exclude-promisor-objects
2232 </dt>
2233 <dd>
2234 <p>
2235 (For internal use only.) Prefilter object traversal at
2236 promisor boundary. This is used with partial clone. This is
2237 stronger than <code>--missing=allow-promisor</code> because it limits the
2238 traversal, rather than just silencing errors about missing
2239 objects.
2240 </p>
2241 </dd>
2243 --no-walk[=(sorted|unsorted)]
2244 </dt>
2245 <dd>
2246 <p>
2247 Only show the given commits, but do not traverse their ancestors.
2248 This has no effect if a range is specified. If the argument
2249 <code>unsorted</code> is given, the commits are shown in the order they were
2250 given on the command line. Otherwise (if <code>sorted</code> or no argument
2251 was given), the commits are shown in reverse chronological order
2252 by commit time.
2253 Cannot be combined with <code>--graph</code>.
2254 </p>
2255 </dd>
2257 --do-walk
2258 </dt>
2259 <dd>
2260 <p>
2261 Overrides a previous <code>--no-walk</code>.
2262 </p>
2263 </dd>
2264 </dl></div>
2265 </div>
2268 <div class="paragraph"><p>Using these options, <a href="git-rev-list.html">git-rev-list(1)</a> will act similar to the
2270 <a href="git-show.html">git-show(1)</a>, and <a href="git-whatchanged.html">git-whatchanged(1)</a></p></div>
2273 --pretty[=<format>]
2274 </dt>
2276 --format=<format>
2277 </dt>
2278 <dd>
2279 <p>
2280 Pretty-print the contents of the commit logs in a given format,
2281 where <em><format></em> can be one of <em>oneline</em>, <em>short</em>, <em>medium</em>,
2282 <em>full</em>, <em>fuller</em>, <em>reference</em>, <em>email</em>, <em>raw</em>, <em>format:<string></em>
2283 and <em>tformat:<string></em>. When <em><format></em> is none of the above,
2284 and has <em>%placeholder</em> in it, it acts as if
2285 <em>--pretty=tformat:<format></em> were given.
2286 </p>
2287 <div class="paragraph"><p>See the "PRETTY FORMATS" section for some additional details for each
2288 format. When <em>=<format></em> part is omitted, it defaults to <em>medium</em>.</p></div>
2291 </dd>
2293 --abbrev-commit
2294 </dt>
2295 <dd>
2296 <p>
2297 Instead of showing the full 40-byte hexadecimal commit object
2298 name, show a prefix that names the object uniquely.
2300 option can be used to specify the minimum length of the prefix.
2301 </p>
2303 people using 80-column terminals.</p></div>
2304 </dd>
2306 --no-abbrev-commit
2307 </dt>
2308 <dd>
2309 <p>
2310 Show the full 40-byte hexadecimal commit object name. This negates
2311 <code>--abbrev-commit</code>, either explicit or implied by other options such
2313 </p>
2314 </dd>
2316 --oneline
2317 </dt>
2318 <dd>
2319 <p>
2321 used together.
2322 </p>
2323 </dd>
2325 --encoding=<encoding>
2326 </dt>
2327 <dd>
2328 <p>
2329 Commit objects record the character encoding used for the log message
2330 in their encoding header; this option can be used to tell the
2331 command to re-code the commit log message in the encoding
2332 preferred by the user. For non plumbing commands this
2333 defaults to UTF-8. Note that if an object claims to be encoded
2334 in <code>X</code> and we are outputting in <code>X</code>, we will output the object
2335 verbatim; this means that invalid sequences in the original
2336 commit may be copied to the output. Likewise, if iconv(3) fails
2337 to convert the commit, we will quietly output the original
2338 object verbatim.
2339 </p>
2340 </dd>
2342 --expand-tabs=<n>
2343 </dt>
2345 --expand-tabs
2346 </dt>
2348 --no-expand-tabs
2349 </dt>
2350 <dd>
2351 <p>
2352 Perform a tab expansion (replace each tab with enough spaces
2353 to fill to the next display column that is multiple of <em><n></em>)
2354 in the log message before showing it in the output.
2355 <code>--expand-tabs</code> is a short-hand for <code>--expand-tabs=8</code>, and
2356 <code>--no-expand-tabs</code> is a short-hand for <code>--expand-tabs=0</code>,
2357 which disables tab expansion.
2358 </p>
2360 message by 4 spaces (i.e. <em>medium</em>, which is the default, <em>full</em>,
2361 and <em>fuller</em>).</p></div>
2362 </dd>
2364 --show-signature
2365 </dt>
2366 <dd>
2367 <p>
2368 Check the validity of a signed commit object by passing the signature
2369 to <code>gpg --verify</code> and show the output.
2370 </p>
2371 </dd>
2373 --relative-date
2374 </dt>
2375 <dd>
2376 <p>
2377 Synonym for <code>--date=relative</code>.
2378 </p>
2379 </dd>
2381 --date=<format>
2382 </dt>
2383 <dd>
2384 <p>
2385 Only takes effect for dates shown in human-readable format, such
2386 as when using <code>--pretty</code>. <code>log.date</code> config variable sets a default
2387 value for the log command’s <code>--date</code> option. By default, dates
2388 are shown in the original time zone (either committer’s or
2389 author’s). If <code>-local</code> is appended to the format (e.g.,
2390 <code>iso-local</code>), the user’s local time zone is used instead.
2391 </p>
2394 <div class="paragraph"><p><code>--date=relative</code> shows dates relative to the current time,
2395 e.g. “2 hours ago”. The <code>-local</code> option has no effect for
2396 <code>--date=relative</code>.</p></div>
2397 <div class="paragraph"><p><code>--date=local</code> is an alias for <code>--date=default-local</code>.</p></div>
2398 <div class="paragraph"><p><code>--date=iso</code> (or <code>--date=iso8601</code>) shows timestamps in a ISO 8601-like format.
2399 The differences to the strict ISO 8601 format are:</p></div>
2401 <li>
2402 <p>
2403 a space instead of the <code>T</code> date/time delimiter
2404 </p>
2405 </li>
2406 <li>
2407 <p>
2408 a space between time and time zone
2409 </p>
2410 </li>
2411 <li>
2412 <p>
2413 no colon between hours and minutes of the time zone
2414 </p>
2415 </li>
2416 </ul></div>
2417 <div class="paragraph"><p><code>--date=iso-strict</code> (or <code>--date=iso8601-strict</code>) shows timestamps in strict
2418 ISO 8601 format.</p></div>
2419 <div class="paragraph"><p><code>--date=rfc</code> (or <code>--date=rfc2822</code>) shows timestamps in RFC 2822
2420 format, often found in email messages.</p></div>
2421 <div class="paragraph"><p><code>--date=short</code> shows only the date, but not the time, in <code>YYYY-MM-DD</code> format.</p></div>
2422 <div class="paragraph"><p><code>--date=raw</code> shows the date as seconds since the epoch (1970-01-01
2423 00:00:00 UTC), followed by a space, and then the timezone as an offset
2424 from UTC (a <code>+</code> or <code>-</code> with four digits; the first two are hours, and
2425 the second two are minutes). I.e., as if the timestamp were formatted
2427 Note that the <code>-local</code> option does not affect the seconds-since-epoch
2428 value (which is always measured in UTC), but does switch the accompanying
2429 timezone value.</p></div>
2430 <div class="paragraph"><p><code>--date=human</code> shows the timezone if the timezone does not match the
2431 current time-zone, and doesn’t print the whole date if that matches
2433 the whole date itself if it’s in the last few days and we can just say
2434 what weekday it was). For older dates the hour and minute is also
2435 omitted.</p></div>
2436 <div class="paragraph"><p><code>--date=unix</code> shows the date as a Unix epoch timestamp (seconds since
2437 1970). As with <code>--raw</code>, this is always in UTC and therefore <code>-local</code>
2438 has no effect.</p></div>
2439 <div class="paragraph"><p><code>--date=format:...</code> feeds the format <code>...</code> to your system <code>strftime</code>,
2440 except for %s, %z, and %Z, which are handled internally.
2441 Use <code>--date=format:%c</code> to show the date in your system locale’s
2442 preferred format. See the <code>strftime</code> manual for a complete list of
2443 format placeholders. When using <code>-local</code>, the correct syntax is
2444 <code>--date=format-local:...</code>.</p></div>
2445 <div class="paragraph"><p><code>--date=default</code> is the default format, and is based on ctime(3)
2446 output. It shows a single line with three-letter day of the week,
2448 format, followed by 4-digit year, plus timezone information, unless
2449 the local time zone is used, e.g. <code>Thu Jan 1 00:00:00 1970 +0000</code>.</p></div>
2450 </div></div>
2451 </dd>
2453 --header
2454 </dt>
2455 <dd>
2456 <p>
2457 Print the contents of the commit in raw-format; each record is
2458 separated with a NUL character.
2459 </p>
2460 </dd>
2462 --no-commit-header
2463 </dt>
2464 <dd>
2465 <p>
2467 the specified format. This has no effect on the built-in formats; only custom
2468 formats are affected.
2469 </p>
2470 </dd>
2472 --commit-header
2473 </dt>
2474 <dd>
2475 <p>
2476 Overrides a previous <code>--no-commit-header</code>.
2477 </p>
2478 </dd>
2480 --parents
2481 </dt>
2482 <dd>
2483 <p>
2485 Also enables parent rewriting, see <em>History Simplification</em> above.
2486 </p>
2487 </dd>
2489 --children
2490 </dt>
2491 <dd>
2492 <p>
2494 Also enables parent rewriting, see <em>History Simplification</em> above.
2495 </p>
2496 </dd>
2498 --timestamp
2499 </dt>
2500 <dd>
2501 <p>
2502 Print the raw commit timestamp.
2503 </p>
2504 </dd>
2506 --left-right
2507 </dt>
2508 <dd>
2509 <p>
2510 Mark which side of a symmetric difference a commit is reachable from.
2511 Commits from the left side are prefixed with <code><</code> and those from
2512 the right with <code>></code>. If combined with <code>--boundary</code>, those
2513 commits are prefixed with <code>-</code>.
2514 </p>
2518 <pre><code> y---b---b branch B
2519 / \ /
2520 / .
2521 / / \
2522 o---x---a---a branch A</code></pre>
2523 </div></div>
2527 <pre><code> $ git rev-list --left-right --boundary --pretty=oneline A...B
2529 >bbbbbbb... 3rd on b
2530 >bbbbbbb... 2nd on b
2531 <aaaaaaa... 3rd on a
2532 <aaaaaaa... 2nd on a
2533 -yyyyyyy... 1st on b
2534 -xxxxxxx... 1st on a</code></pre>
2535 </div></div>
2536 </dd>
2538 --graph
2539 </dt>
2540 <dd>
2541 <p>
2542 Draw a text-based graphical representation of the commit history
2543 on the left hand side of the output. This may cause extra lines
2544 to be printed in between commits, in order for the graph history
2545 to be drawn properly.
2546 Cannot be combined with <code>--no-walk</code>.
2547 </p>
2548 <div class="paragraph"><p>This enables parent rewriting, see <em>History Simplification</em> above.</p></div>
2549 <div class="paragraph"><p>This implies the <code>--topo-order</code> option by default, but the
2550 <code>--date-order</code> option may also be specified.</p></div>
2551 </dd>
2553 --show-linear-break[=<barrier>]
2554 </dt>
2555 <dd>
2556 <p>
2557 When --graph is not used, all history branches are flattened
2558 which can make it hard to see that the two consecutive commits
2559 do not belong to a linear branch. This option puts a barrier
2560 in between them in that case. If <code><barrier></code> is specified, it
2561 is the string that will be shown instead of the default one.
2562 </p>
2563 </dd>
2565 --count
2566 </dt>
2567 <dd>
2568 <p>
2569 Print a number stating how many commits would have been
2570 listed, and suppress all other output. When used together
2571 with <code>--left-right</code>, instead print the counts for left and
2572 right commits, separated by a tab. When used together with
2573 <code>--cherry-mark</code>, omit patch equivalent commits from these
2574 counts and print the count for equivalent commits separated
2575 by a tab.
2576 </p>
2577 </dd>
2578 </dl></div>
2579 </div>
2580 </div>
2581 </div>
2586 is not <em>oneline</em>, <em>email</em> or <em>raw</em>, an additional line is
2587 inserted before the <em>Author:</em> line. This line begins with
2589 separated by spaces. Note that the listed commits may not
2590 necessarily be the list of the <strong>direct</strong> parent commits if you
2591 have limited your view of history: for example, if you are
2592 only interested in changes related to a certain directory or
2593 file.</p></div>
2595 additional formats by setting a pretty.<name>
2596 config option to either another format name, or a
2597 <em>format:</em> string, as described below (see
2599 built-in formats:</p></div>
2601 <li>
2602 <p>
2603 <em>oneline</em>
2604 </p>
2607 <pre><code><hash> <title-line></code></pre>
2608 </div></div>
2610 </li>
2611 <li>
2612 <p>
2613 <em>short</em>
2614 </p>
2617 <pre><code>commit <hash>
2618 Author: <author></code></pre>
2619 </div></div>
2622 <pre><code><title-line></code></pre>
2623 </div></div>
2624 </li>
2625 <li>
2626 <p>
2627 <em>medium</em>
2628 </p>
2631 <pre><code>commit <hash>
2632 Author: <author>
2633 Date: <author-date></code></pre>
2634 </div></div>
2637 <pre><code><title-line></code></pre>
2638 </div></div>
2641 <pre><code><full-commit-message></code></pre>
2642 </div></div>
2643 </li>
2644 <li>
2645 <p>
2646 <em>full</em>
2647 </p>
2650 <pre><code>commit <hash>
2651 Author: <author>
2652 Commit: <committer></code></pre>
2653 </div></div>
2656 <pre><code><title-line></code></pre>
2657 </div></div>
2660 <pre><code><full-commit-message></code></pre>
2661 </div></div>
2662 </li>
2663 <li>
2664 <p>
2665 <em>fuller</em>
2666 </p>
2669 <pre><code>commit <hash>
2670 Author: <author>
2671 AuthorDate: <author-date>
2672 Commit: <committer>
2673 CommitDate: <committer-date></code></pre>
2674 </div></div>
2677 <pre><code><title-line></code></pre>
2678 </div></div>
2681 <pre><code><full-commit-message></code></pre>
2682 </div></div>
2683 </li>
2684 <li>
2685 <p>
2686 <em>reference</em>
2687 </p>
2690 <pre><code><abbrev-hash> (<title-line>, <short-author-date>)</code></pre>
2691 </div></div>
2692 <div class="paragraph"><p>This format is used to refer to another commit in a commit message and
2693 is the same as <code>--pretty='format:%C(auto)%h (%s, %ad)'</code>. By default,
2694 the date is formatted with <code>--date=short</code> unless another <code>--date</code> option
2695 is explicitly specified. As with any <code>format:</code> with format
2696 placeholders, its output is not affected by other options like
2697 <code>--decorate</code> and <code>--walk-reflogs</code>.</p></div>
2698 </li>
2699 <li>
2700 <p>
2701 <em>email</em>
2702 </p>
2705 <pre><code>From <hash> <date>
2706 From: <author>
2707 Date: <author-date>
2708 Subject: [PATCH] <title-line></code></pre>
2709 </div></div>
2712 <pre><code><full-commit-message></code></pre>
2713 </div></div>
2714 </li>
2715 <li>
2716 <p>
2717 <em>mboxrd</em>
2718 </p>
2719 <div class="paragraph"><p>Like <em>email</em>, but lines in the commit message starting with "From "
2721 confused as starting a new commit.</p></div>
2722 </li>
2723 <li>
2724 <p>
2725 <em>raw</em>
2726 </p>
2728 stored in the commit object. Notably, the hashes are
2729 displayed in full, regardless of whether --abbrev or
2730 --no-abbrev are used, and <em>parents</em> information show the
2731 true parent commits, without taking grafts or history
2732 simplification into account. Note that this format affects the way
2733 commits are displayed, but not the way the diff is shown e.g. with
2734 <code>git log --raw</code>. To get full object names in a raw diff format,
2735 use <code>--no-abbrev</code>.</p></div>
2736 </li>
2737 <li>
2738 <p>
2739 <em>format:<format-string></em>
2740 </p>
2741 <div class="paragraph"><p>The <em>format:<format-string></em> format allows you to specify which information
2742 you want to show. It works a little bit like printf format,
2743 with the notable exception that you get a newline with <em>%n</em>
2744 instead of <em>\n</em>.</p></div>
2745 <div class="paragraph"><p>E.g, <em>format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"</em>
2746 would show something like this:</p></div>
2749 <pre><code>The author of fe6e0ee was Junio C Hamano, 23 hours ago
2750 The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<</code></pre>
2751 </div></div>
2754 <li>
2755 <p>
2756 Placeholders that expand to a single literal character:
2757 </p>
2760 <em>%n</em>
2761 </dt>
2762 <dd>
2763 <p>
2764 newline
2765 </p>
2766 </dd>
2768 <em>%%</em>
2769 </dt>
2770 <dd>
2771 <p>
2772 a raw <em>%</em>
2773 </p>
2774 </dd>
2776 <em>%x00</em>
2777 </dt>
2778 <dd>
2779 <p>
2780 print a byte from a hex code
2781 </p>
2782 </dd>
2783 </dl></div>
2784 </li>
2785 <li>
2786 <p>
2787 Placeholders that affect formatting of later placeholders:
2788 </p>
2791 <em>%Cred</em>
2792 </dt>
2793 <dd>
2794 <p>
2795 switch color to red
2796 </p>
2797 </dd>
2799 <em>%Cgreen</em>
2800 </dt>
2801 <dd>
2802 <p>
2803 switch color to green
2804 </p>
2805 </dd>
2807 <em>%Cblue</em>
2808 </dt>
2809 <dd>
2810 <p>
2811 switch color to blue
2812 </p>
2813 </dd>
2815 <em>%Creset</em>
2816 </dt>
2817 <dd>
2818 <p>
2819 reset color
2820 </p>
2821 </dd>
2823 <em>%C(…)</em>
2824 </dt>
2825 <dd>
2826 <p>
2827 color specification, as described under Values in the
2829 default, colors are shown only when enabled for log output
2830 (by <code>color.diff</code>, <code>color.ui</code>, or <code>--color</code>, and respecting
2831 the <code>auto</code> settings of the former if we are going to a
2832 terminal). <code>%C(auto,...)</code> is accepted as a historical
2833 synonym for the default (e.g., <code>%C(auto,red)</code>). Specifying
2834 <code>%C(always,...)</code> will show the colors even when color is
2835 not otherwise enabled (though consider just using
2836 <code>--color=always</code> to enable color for the whole output,
2837 including this format and anything else git might color).
2838 <code>auto</code> alone (i.e. <code>%C(auto)</code>) will turn on auto coloring
2839 on the next placeholders until the color is switched
2840 again.
2841 </p>
2842 </dd>
2844 <em>%m</em>
2845 </dt>
2846 <dd>
2847 <p>
2848 left (<code><</code>), right (<code>></code>) or boundary (<code>-</code>) mark
2849 </p>
2850 </dd>
2852 <em>%w([<w>[,<i1>[,<i2>]]])</em>
2853 </dt>
2854 <dd>
2855 <p>
2856 switch line wrapping, like the -w option of
2858 </p>
2859 </dd>
2861 <em>%<( <N> [,trunc|ltrunc|mtrunc])</em>
2862 </dt>
2863 <dd>
2864 <p>
2865 make the next placeholder take at
2866 least N column widths, padding spaces on
2867 the right if necessary. Optionally
2868 truncate (with ellipsis <em>..</em>) at the left (ltrunc) <code>..ft</code>,
2869 the middle (mtrunc) <code>mi..le</code>, or the end
2870 (trunc) <code>rig..</code>, if the output is longer than
2871 N columns.
2872 Note 1: that truncating
2873 only works correctly with N >= 2.
2874 Note 2: spaces around the N and M (see below)
2875 values are optional.
2876 Note 3: Emojis and other wide characters
2877 will take two display columns, which may
2878 over-run column boundaries.
2879 Note 4: decomposed character combining marks
2880 may be misplaced at padding boundaries.
2881 </p>
2882 </dd>
2884 <em>%<|( <M> )</em>
2885 </dt>
2886 <dd>
2887 <p>
2888 make the next placeholder take at least until Mth
2889 display column, padding spaces on the right if necessary.
2890 Use negative M values for column positions measured
2891 from the right hand edge of the terminal window.
2892 </p>
2893 </dd>
2895 <em>%>( <N> )</em>, <em>%>|( <M> )</em>
2896 </dt>
2897 <dd>
2898 <p>
2899 similar to <em>%<( <N> )</em>, <em>%<|( <M> )</em> respectively,
2900 but padding spaces on the left
2901 </p>
2902 </dd>
2904 <em>%>>( <N> )</em>, <em>%>>|( <M> )</em>
2905 </dt>
2906 <dd>
2907 <p>
2908 similar to <em>%>( <N> )</em>, <em>%>|( <M> )</em>
2909 respectively, except that if the next
2910 placeholder takes more spaces than given and
2911 there are spaces on its left, use those
2912 spaces
2913 </p>
2914 </dd>
2916 <em>%><( <N> )</em>, <em>%><|( <M> )</em>
2917 </dt>
2918 <dd>
2919 <p>
2920 similar to <em>%<( <N> )</em>, <em>%<|( <M> )</em>
2921 respectively, but padding both sides
2922 (i.e. the text is centered)
2923 </p>
2924 </dd>
2925 </dl></div>
2926 </li>
2927 <li>
2928 <p>
2929 Placeholders that expand to information extracted from the commit:
2930 </p>
2933 <em>%H</em>
2934 </dt>
2935 <dd>
2936 <p>
2937 commit hash
2938 </p>
2939 </dd>
2941 <em>%h</em>
2942 </dt>
2943 <dd>
2944 <p>
2945 abbreviated commit hash
2946 </p>
2947 </dd>
2949 <em>%T</em>
2950 </dt>
2951 <dd>
2952 <p>
2953 tree hash
2954 </p>
2955 </dd>
2957 <em>%t</em>
2958 </dt>
2959 <dd>
2960 <p>
2961 abbreviated tree hash
2962 </p>
2963 </dd>
2965 <em>%P</em>
2966 </dt>
2967 <dd>
2968 <p>
2969 parent hashes
2970 </p>
2971 </dd>
2973 <em>%p</em>
2974 </dt>
2975 <dd>
2976 <p>
2977 abbreviated parent hashes
2978 </p>
2979 </dd>
2981 <em>%an</em>
2982 </dt>
2983 <dd>
2984 <p>
2985 author name
2986 </p>
2987 </dd>
2989 <em>%aN</em>
2990 </dt>
2991 <dd>
2992 <p>
2995 </p>
2996 </dd>
2998 <em>%ae</em>
2999 </dt>
3000 <dd>
3001 <p>
3002 author email
3003 </p>
3004 </dd>
3006 <em>%aE</em>
3007 </dt>
3008 <dd>
3009 <p>
3012 </p>
3013 </dd>
3015 <em>%al</em>
3016 </dt>
3017 <dd>
3018 <p>
3019 author email local-part (the part before the <em>@</em> sign)
3020 </p>
3021 </dd>
3023 <em>%aL</em>
3024 </dt>
3025 <dd>
3026 <p>
3027 author local-part (see <em>%al</em>) respecting .mailmap, see
3029 </p>
3030 </dd>
3032 <em>%ad</em>
3033 </dt>
3034 <dd>
3035 <p>
3036 author date (format respects --date= option)
3037 </p>
3038 </dd>
3040 <em>%aD</em>
3041 </dt>
3042 <dd>
3043 <p>
3044 author date, RFC2822 style
3045 </p>
3046 </dd>
3048 <em>%ar</em>
3049 </dt>
3050 <dd>
3051 <p>
3052 author date, relative
3053 </p>
3054 </dd>
3056 <em>%at</em>
3057 </dt>
3058 <dd>
3059 <p>
3060 author date, UNIX timestamp
3061 </p>
3062 </dd>
3064 <em>%ai</em>
3065 </dt>
3066 <dd>
3067 <p>
3068 author date, ISO 8601-like format
3069 </p>
3070 </dd>
3072 <em>%aI</em>
3073 </dt>
3074 <dd>
3075 <p>
3076 author date, strict ISO 8601 format
3077 </p>
3078 </dd>
3080 <em>%as</em>
3081 </dt>
3082 <dd>
3083 <p>
3084 author date, short format (<code>YYYY-MM-DD</code>)
3085 </p>
3086 </dd>
3088 <em>%ah</em>
3089 </dt>
3090 <dd>
3091 <p>
3092 author date, human style (like the <code>--date=human</code> option of
3094 </p>
3095 </dd>
3097 <em>%cn</em>
3098 </dt>
3099 <dd>
3100 <p>
3101 committer name
3102 </p>
3103 </dd>
3105 <em>%cN</em>
3106 </dt>
3107 <dd>
3108 <p>
3109 committer name (respecting .mailmap, see
3111 </p>
3112 </dd>
3114 <em>%ce</em>
3115 </dt>
3116 <dd>
3117 <p>
3118 committer email
3119 </p>
3120 </dd>
3122 <em>%cE</em>
3123 </dt>
3124 <dd>
3125 <p>
3126 committer email (respecting .mailmap, see
3128 </p>
3129 </dd>
3131 <em>%cl</em>
3132 </dt>
3133 <dd>
3134 <p>
3135 committer email local-part (the part before the <em>@</em> sign)
3136 </p>
3137 </dd>
3139 <em>%cL</em>
3140 </dt>
3141 <dd>
3142 <p>
3143 committer local-part (see <em>%cl</em>) respecting .mailmap, see
3145 </p>
3146 </dd>
3148 <em>%cd</em>
3149 </dt>
3150 <dd>
3151 <p>
3152 committer date (format respects --date= option)
3153 </p>
3154 </dd>
3156 <em>%cD</em>
3157 </dt>
3158 <dd>
3159 <p>
3160 committer date, RFC2822 style
3161 </p>
3162 </dd>
3164 <em>%cr</em>
3165 </dt>
3166 <dd>
3167 <p>
3168 committer date, relative
3169 </p>
3170 </dd>
3172 <em>%ct</em>
3173 </dt>
3174 <dd>
3175 <p>
3176 committer date, UNIX timestamp
3177 </p>
3178 </dd>
3180 <em>%ci</em>
3181 </dt>
3182 <dd>
3183 <p>
3184 committer date, ISO 8601-like format
3185 </p>
3186 </dd>
3188 <em>%cI</em>
3189 </dt>
3190 <dd>
3191 <p>
3192 committer date, strict ISO 8601 format
3193 </p>
3194 </dd>
3196 <em>%cs</em>
3197 </dt>
3198 <dd>
3199 <p>
3200 committer date, short format (<code>YYYY-MM-DD</code>)
3201 </p>
3202 </dd>
3204 <em>%ch</em>
3205 </dt>
3206 <dd>
3207 <p>
3208 committer date, human style (like the <code>--date=human</code> option of
3210 </p>
3211 </dd>
3213 <em>%d</em>
3214 </dt>
3215 <dd>
3216 <p>
3218 </p>
3219 </dd>
3221 <em>%D</em>
3222 </dt>
3223 <dd>
3224 <p>
3226 </p>
3227 </dd>
3229 <em>%(describe[:options])</em>
3230 </dt>
3231 <dd>
3232 <p>
3233 human-readable name, like
3235 undescribable commits. The <code>describe</code> string
3236 may be followed by a colon and zero or more
3237 comma-separated options. Descriptions can be
3238 inconsistent when tags are added or removed at
3239 the same time.
3240 </p>
3242 <li>
3243 <p>
3244 <em>tags[=<bool-value>]</em>: Instead of only considering annotated tags,
3245 consider lightweight tags as well.
3246 </p>
3247 </li>
3248 <li>
3249 <p>
3250 <em>abbrev=<number></em>: Instead of using the default number of hexadecimal digits
3251 (which will vary according to the number of objects in the repository with a
3252 default of 7) of the abbreviated object name, use <number> digits, or as many
3253 digits as needed to form a unique object name.
3254 </p>
3255 </li>
3256 <li>
3257 <p>
3258 <em>match=<pattern></em>: Only consider tags matching the given
3260 </p>
3261 </li>
3262 <li>
3263 <p>
3264 <em>exclude=<pattern></em>: Do not consider tags matching the given
3266 </p>
3267 </li>
3268 </ul></div>
3269 </dd>
3271 <em>%S</em>
3272 </dt>
3273 <dd>
3274 <p>
3275 ref name given on the command line by which the commit was reached
3276 (like <code>git log --source</code>), only works with <code>git log</code>
3277 </p>
3278 </dd>
3280 <em>%e</em>
3281 </dt>
3282 <dd>
3283 <p>
3284 encoding
3285 </p>
3286 </dd>
3288 <em>%s</em>
3289 </dt>
3290 <dd>
3291 <p>
3292 subject
3293 </p>
3294 </dd>
3296 <em>%f</em>
3297 </dt>
3298 <dd>
3299 <p>
3300 sanitized subject line, suitable for a filename
3301 </p>
3302 </dd>
3304 <em>%b</em>
3305 </dt>
3306 <dd>
3307 <p>
3308 body
3309 </p>
3310 </dd>
3312 <em>%B</em>
3313 </dt>
3314 <dd>
3315 <p>
3316 raw body (unwrapped subject and body)
3317 </p>
3318 </dd>
3320 <em>%GG</em>
3321 </dt>
3322 <dd>
3323 <p>
3324 raw verification message from GPG for a signed commit
3325 </p>
3326 </dd>
3328 <em>%G?</em>
3329 </dt>
3330 <dd>
3331 <p>
3340 </p>
3341 </dd>
3343 <em>%GS</em>
3344 </dt>
3345 <dd>
3346 <p>
3347 show the name of the signer for a signed commit
3348 </p>
3349 </dd>
3351 <em>%GK</em>
3352 </dt>
3353 <dd>
3354 <p>
3355 show the key used to sign a signed commit
3356 </p>
3357 </dd>
3359 <em>%GF</em>
3360 </dt>
3361 <dd>
3362 <p>
3363 show the fingerprint of the key used to sign a signed commit
3364 </p>
3365 </dd>
3367 <em>%GP</em>
3368 </dt>
3369 <dd>
3370 <p>
3371 show the fingerprint of the primary key whose subkey was used
3372 to sign a signed commit
3373 </p>
3374 </dd>
3376 <em>%GT</em>
3377 </dt>
3378 <dd>
3379 <p>
3380 show the trust level for the key used to sign a signed commit
3381 </p>
3382 </dd>
3384 <em>%gD</em>
3385 </dt>
3386 <dd>
3387 <p>
3388 reflog selector, e.g., <code>refs/stash@{1}</code> or <code>refs/stash@{2
3389 minutes ago}</code>; the format follows the rules described for the
3390 <code>-g</code> option. The portion before the <code>@</code> is the refname as
3391 given on the command line (so <code>git log -g refs/heads/master</code>
3392 would yield <code>refs/heads/master@{0}</code>).
3393 </p>
3394 </dd>
3396 <em>%gd</em>
3397 </dt>
3398 <dd>
3399 <p>
3400 shortened reflog selector; same as <code>%gD</code>, but the refname
3401 portion is shortened for human readability (so
3402 <code>refs/heads/master</code> becomes just <code>master</code>).
3403 </p>
3404 </dd>
3406 <em>%gn</em>
3407 </dt>
3408 <dd>
3409 <p>
3410 reflog identity name
3411 </p>
3412 </dd>
3414 <em>%gN</em>
3415 </dt>
3416 <dd>
3417 <p>
3418 reflog identity name (respecting .mailmap, see
3420 </p>
3421 </dd>
3423 <em>%ge</em>
3424 </dt>
3425 <dd>
3426 <p>
3427 reflog identity email
3428 </p>
3429 </dd>
3431 <em>%gE</em>
3432 </dt>
3433 <dd>
3434 <p>
3435 reflog identity email (respecting .mailmap, see
3437 </p>
3438 </dd>
3440 <em>%gs</em>
3441 </dt>
3442 <dd>
3443 <p>
3444 reflog subject
3445 </p>
3446 </dd>
3448 <em>%(trailers[:options])</em>
3449 </dt>
3450 <dd>
3451 <p>
3452 display the trailers of the body as
3453 interpreted by
3455 <code>trailers</code> string may be followed by a colon
3456 and zero or more comma-separated options.
3457 If any option is provided multiple times the
3458 last occurrence wins.
3459 </p>
3461 <li>
3462 <p>
3463 <em>key=<key></em>: only show trailers with specified <key>. Matching is done
3464 case-insensitively and trailing colon is optional. If option is
3465 given multiple times trailer lines matching any of the keys are
3466 shown. This option automatically enables the <code>only</code> option so that
3467 non-trailer lines in the trailer block are hidden. If that is not
3468 desired it can be disabled with <code>only=false</code>. E.g.,
3469 <code>%(trailers:key=Reviewed-by)</code> shows trailer lines with key
3470 <code>Reviewed-by</code>.
3471 </p>
3472 </li>
3473 <li>
3474 <p>
3475 <em>only[=<bool>]</em>: select whether non-trailer lines from the trailer
3476 block should be included.
3477 </p>
3478 </li>
3479 <li>
3480 <p>
3481 <em>separator=<sep></em>: specify a separator inserted between trailer
3482 lines. When this option is not given each trailer line is
3483 terminated with a line feed character. The string <sep> may contain
3484 the literal formatting codes described above. To use comma as
3485 separator one must use <code>%x2C</code> as it would otherwise be parsed as
3486 next option. E.g., <code>%(trailers:key=Ticket,separator=%x2C )</code>
3488 and a space.
3489 </p>
3490 </li>
3491 <li>
3492 <p>
3493 <em>unfold[=<bool>]</em>: make it behave as if interpret-trailer’s <code>--unfold</code>
3494 option was given. E.g.,
3495 <code>%(trailers:only,unfold=true)</code> unfolds and shows all trailer lines.
3496 </p>
3497 </li>
3498 <li>
3499 <p>
3500 <em>keyonly[=<bool>]</em>: only show the key part of the trailer.
3501 </p>
3502 </li>
3503 <li>
3504 <p>
3505 <em>valueonly[=<bool>]</em>: only show the value part of the trailer.
3506 </p>
3507 </li>
3508 <li>
3509 <p>
3510 <em>key_value_separator=<sep></em>: specify a separator inserted between
3511 trailer lines. When this option is not given each trailer key-value
3513 as <em>separator=<sep></em> above.
3514 </p>
3515 </li>
3516 </ul></div>
3517 </dd>
3518 </dl></div>
3519 </li>
3520 </ul></div>
3521 </li>
3522 </ul></div>
3524 <table><tr>
3527 </td>
3529 revision traversal engine. For example, the <code>%g*</code> reflog options will
3530 insert an empty string unless we are traversing reflog entries (e.g., by
3531 <code>git log -g</code>). The <code>%d</code> and <code>%D</code> placeholders will use the "short"
3532 decoration format if <code>--decorate</code> was not already provided on the command
3533 line.</td>
3534 </tr></table>
3535 </div>
3536 <div class="paragraph"><p>The boolean options accept an optional value <code>[=<bool-value>]</code>. The values
3537 <code>true</code>, <code>false</code>, <code>on</code>, <code>off</code> etc. are all accepted. See the "boolean"
3539 option is given with no value, it’s enabled.</p></div>
3540 <div class="paragraph"><p>If you add a <code>+</code> (plus sign) after <em>%</em> of a placeholder, a line-feed
3541 is inserted immediately before the expansion if and only if the
3542 placeholder expands to a non-empty string.</p></div>
3543 <div class="paragraph"><p>If you add a <code>-</code> (minus sign) after <em>%</em> of a placeholder, all consecutive
3544 line-feeds immediately preceding the expansion are deleted if and only if the
3545 placeholder expands to an empty string.</p></div>
3547 is inserted immediately before the expansion if and only if the
3548 placeholder expands to a non-empty string.</p></div>
3550 <li>
3551 <p>
3552 <em>tformat:</em>
3553 </p>
3554 <div class="paragraph"><p>The <em>tformat:</em> format works exactly like <em>format:</em>, except that it
3556 other words, each commit has the message terminator character (usually a
3557 newline) appended, rather than a separator placed between entries.
3558 This means that the final entry of a single-line format will be properly
3560 For example:</p></div>
3563 <pre><code>$ git log -2 --pretty=format:%h 4da45bef \
3565 4da45be
3566 7134973 -- NO NEWLINE
3568 $ git log -2 --pretty=tformat:%h 4da45bef \
3570 4da45be
3571 7134973</code></pre>
3572 </div></div>
3573 <div class="paragraph"><p>In addition, any unrecognized string that has a <code>%</code> in it is interpreted
3574 as if it has <code>tformat:</code> in front of it. For example, these two are
3575 equivalent:</p></div>
3578 <pre><code>$ git log -2 --pretty=tformat:%h 4da45bef
3579 $ git log -2 --pretty=%h 4da45bef</code></pre>
3580 </div></div>
3581 </li>
3582 </ul></div>
3583 </div>
3584 </div>
3589 <li>
3590 <p>
3591 Print the list of commits reachable from the current branch.
3592 </p>
3595 <pre><code>git rev-list HEAD</code></pre>
3596 </div></div>
3597 </li>
3598 <li>
3599 <p>
3600 Print the list of commits on this branch, but not present in the
3601 upstream branch.
3602 </p>
3605 <pre><code>git rev-list @{upstream}..HEAD</code></pre>
3606 </div></div>
3607 </li>
3608 <li>
3609 <p>
3610 Format commits with their author and commit message (see also the
3612 </p>
3615 <pre><code>git rev-list --format=medium HEAD</code></pre>
3616 </div></div>
3617 </li>
3618 <li>
3619 <p>
3620 Format commits along with their diffs (see also the porcelain
3622 </p>
3625 <pre><code>git rev-list HEAD |
3626 git diff-tree --stdin --format=medium -p</code></pre>
3627 </div></div>
3628 </li>
3629 <li>
3630 <p>
3631 Print the list of commits on the current branch that touched any
3632 file in the <code>Documentation</code> directory.
3633 </p>
3636 <pre><code>git rev-list HEAD -- Documentation/</code></pre>
3637 </div></div>
3638 </li>
3639 <li>
3640 <p>
3641 Print the list of commits authored by you in the past year, on
3642 any branch, tag, or other ref.
3643 </p>
3646 <pre><code>git rev-list --author=you@example.com --since=1.year.ago --all</code></pre>
3647 </div></div>
3648 </li>
3649 <li>
3650 <p>
3651 Print the list of objects reachable from the current branch (i.e., all
3652 commits and the blobs and trees they contain).
3653 </p>
3656 <pre><code>git rev-list --objects HEAD</code></pre>
3657 </div></div>
3658 </li>
3659 <li>
3660 <p>
3661 Compare the disk size of all reachable objects, versus those
3662 reachable from reflogs, versus the total packed size. This can tell
3663 you whether running <code>git repack -ad</code> might reduce the repository size
3664 (by dropping unreachable objects), and whether expiring reflogs might
3665 help.
3666 </p>
3669 <pre><code># reachable objects
3670 git rev-list --disk-usage --objects --all
3671 # plus reflogs
3672 git rev-list --disk-usage --objects --all --reflog
3673 # total disk size used
3674 du -c .git/objects/pack/*.pack .git/objects/??/*
3676 git count-objects -v</code></pre>
3677 </div></div>
3678 </li>
3679 <li>
3680 <p>
3681 Report the disk size of each branch, not including objects used by the
3682 current branch. This can find outliers that are contributing to a
3683 bloated repository size (e.g., because somebody accidentally committed
3684 large build artifacts).
3685 </p>
3688 <pre><code>git for-each-ref --format='%(refname)' |
3689 while read branch
3690 do
3691 size=$(git rev-list --disk-usage --objects HEAD..$branch)
3693 done |
3694 sort -n</code></pre>
3695 </div></div>
3696 </li>
3697 <li>
3698 <p>
3699 Compare the on-disk size of branches in one group of refs, excluding
3700 another. If you co-mingle objects from multiple remotes in a single
3701 repository, this can show which remotes are contributing to the
3702 repository size (taking the size of <code>origin</code> as a baseline).
3703 </p>
3706 <pre><code>git rev-list --disk-usage --objects --remotes=$suspect --not --remotes=origin</code></pre>
3707 </div></div>
3708 </li>
3709 </ul></div>
3710 </div>
3711 </div>
3716 </div>
3717 </div>
3718 </div>
3722 Last updated
3723 2022-10-28 11:53:56 PDT
3724 </div>
3725 </div>
3726 </body>
3727 </html>