| blob | 66de3d04d823452e2eccc9053a637906c48ad016 |
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-log(1) Manual Page
739 </h1>
742 <p>git-log -
743 Show commit logs
744 </p>
745 </div>
746 </div>
752 <pre class="content"><em>git log</em> [<options>] [<revision-range>] [[--] <path>…]</pre>
754 </div></div>
755 </div>
756 </div>
761 <div class="paragraph"><p>List commits that are reachable by following the <code>parent</code> links from the
762 given commit(s), but exclude commits that are reachable from the one(s)
764 chronological order by default.</p></div>
765 <div class="paragraph"><p>You can think of this as a set operation. Commits reachable from any of
766 the commits given on the command line form a set, and then commits reachable
768 set. The remaining commits are what comes out in the command’s output.
769 Various other options and paths parameters can be used to further limit the
770 result.</p></div>
775 </div></div>
776 <div class="paragraph"><p>means "list all the commits which are reachable from <em>foo</em> or <em>bar</em>, but
778 <div class="paragraph"><p>A special notation "<em><commit1></em>..<em><commit2></em>" can be used as a
779 short-hand for "^<em><commit1></em> <em><commit2></em>". For example, either of
780 the following may be used interchangeably:</p></div>
783 <pre><code>$ git log origin..HEAD
784 $ git log HEAD ^origin</code></pre>
785 </div></div>
786 <div class="paragraph"><p>Another special notation is "<em><commit1></em>…<em><commit2></em>" which is useful
787 for merges. The resulting set of commits is the symmetric difference
788 between the two operands. The following two commands are equivalent:</p></div>
791 <pre><code>$ git log A B --not $(git merge-base --all A B)
792 $ git log A...B</code></pre>
793 </div></div>
794 <div class="paragraph"><p>The command takes options applicable to the <a href="git-rev-list.html">git-rev-list(1)</a>
795 command to control what is shown and how, and options applicable to
797 each commit introduces are shown.</p></div>
798 </div>
799 </div>
805 --follow
806 </dt>
807 <dd>
808 <p>
809 Continue listing the history of a file beyond renames
810 (works only for a single file).
811 </p>
812 </dd>
814 --no-decorate
815 </dt>
817 --decorate[=short|full|auto|no]
818 </dt>
819 <dd>
820 <p>
825 specified, then if the output is going to a terminal, the ref names
830 </p>
831 </dd>
834 </dt>
837 </dt>
838 <dd>
839 <p>
840 For each candidate reference, do not use it for decoration if it
846 </p>
847 <div class="paragraph"><p>If none of these options or config settings are given, then references are
848 used as decoration if they match <code>HEAD</code>, <code>refs/heads/</code>, <code>refs/remotes/</code>,
850 </dd>
852 --clear-decorations
853 </dt>
854 <dd>
855 <p>
858 decoration filter to include all references. This option is
861 </p>
862 </dd>
864 --source
865 </dt>
866 <dd>
867 <p>
868 Print out the ref name given on the command line by which each
869 commit was reached.
870 </p>
871 </dd>
873 --[no-]mailmap
874 </dt>
876 --[no-]use-mailmap
877 </dt>
878 <dd>
879 <p>
880 Use mailmap file to map author and committer names and email
881 addresses to canonical real names and email addresses. See
883 </p>
884 </dd>
886 --full-diff
887 </dt>
888 <dd>
889 <p>
891 touch the specified paths, and diffs about the same specified
892 paths. With this, the full diff is shown for commits that touch
893 the specified paths; this means that "<path>…" limits only
894 commits, and doesn’t limit diff for those commits.
895 </p>
898 </dd>
900 --log-size
901 </dt>
902 <dd>
903 <p>
907 output by allowing them to allocate space in advance.
908 </p>
909 </dd>
912 </dt>
915 </dt>
916 <dd>
917 <p>
919 or by the function name regex <em><funcname></em>, within the <em><file></em>. You may
920 not give any pathspec limiters. This is currently limited to
921 a walk starting from a single revision, i.e., you may only
922 give zero or one positive revision arguments, and
923 <em><start></em> and <em><end></em> (or <em><funcname></em>) must exist in the starting revision.
926 (namely <code>--raw</code>, <code>--numstat</code>, <code>--shortstat</code>, <code>--dirstat</code>, <code>--summary</code>,
927 <code>--name-only</code>, <code>--name-status</code>, <code>--check</code>) are not currently implemented.
928 </p>
929 <div class="paragraph"><p><em><start></em> and <em><end></em> can take one of these forms:</p></div>
931 <li>
932 <p>
933 number
934 </p>
935 <div class="paragraph"><p>If <em><start></em> or <em><end></em> is a number, it specifies an
937 </li>
938 <li>
939 <p>
941 </p>
948 </li>
949 <li>
950 <p>
951 +offset or -offset
952 </p>
955 </li>
956 </ul></div>
957 <div class="paragraph"><p>If <code>:<funcname></code> is given in place of <em><start></em> and <em><end></em>, it is a
958 regular expression that denotes the range from the first funcname line
959 that matches <em><funcname></em>, up to the next funcname line. <code>:<funcname></code>
965 </dd>
968 </dt>
969 <dd>
970 <p>
971 Show only commits in the specified revision range. When no
974 specifies all the commits reachable from the current commit
978 </p>
979 </dd>
982 </dt>
983 <dd>
984 <p>
985 Show only commits that are enough to explain how the files
986 that match the specified paths came to be. See <em>History
987 Simplification</em> below for details and other simplification
988 modes.
989 </p>
990 <div class="paragraph"><p>Paths may need to be prefixed with <code>--</code> to separate them from
991 options or the revision range, when confusion arises.</p></div>
992 </dd>
993 </dl></div>
997 special notations explained in the description, additional commit
998 limiting may be applied.</p></div>
1000 <code>--since=<date1></code> limits to commits newer than <code><date1></code>, and using it
1008 </dt>
1011 </dt>
1014 </dt>
1015 <dd>
1016 <p>
1017 Limit the number of commits to output.
1018 </p>
1019 </dd>
1022 </dt>
1023 <dd>
1024 <p>
1026 </p>
1027 </dd>
1030 </dt>
1033 </dt>
1034 <dd>
1035 <p>
1036 Show commits more recent than a specific date.
1037 </p>
1038 </dd>
1041 </dt>
1042 <dd>
1043 <p>
1044 Show all commits more recent than a specific date. This visits
1045 all commits in the range, rather than stopping at the first commit which
1046 is older than a specific date.
1047 </p>
1048 </dd>
1051 </dt>
1054 </dt>
1055 <dd>
1056 <p>
1057 Show commits older than a specific date.
1058 </p>
1059 </dd>
1062 </dt>
1065 </dt>
1066 <dd>
1067 <p>
1068 Limit the commits output to ones with author/committer
1069 header lines that match the specified pattern (regular
1071 commits whose author matches any of the given patterns are
1073 </p>
1074 </dd>
1077 </dt>
1078 <dd>
1079 <p>
1080 Limit the commits output to ones with reflog entries that
1081 match the specified pattern (regular expression). With
1083 matches any of the given patterns are chosen. It is an
1085 </p>
1086 </dd>
1089 </dt>
1090 <dd>
1091 <p>
1092 Limit the commits output to ones with log message that
1093 matches the specified pattern (regular expression). With
1095 matches any of the given patterns are chosen (but see
1097 </p>
1098 <div class="paragraph"><p>When <code>--notes</code> is in effect, the message from the notes is
1099 matched as if it were part of the log message.</p></div>
1100 </dd>
1102 --all-match
1103 </dt>
1104 <dd>
1105 <p>
1107 instead of ones that match at least one.
1108 </p>
1109 </dd>
1111 --invert-grep
1112 </dt>
1113 <dd>
1114 <p>
1115 Limit the commits output to ones with log message that do not
1117 </p>
1118 </dd>
1120 -i
1121 </dt>
1123 --regexp-ignore-case
1124 </dt>
1125 <dd>
1126 <p>
1127 Match the regular expression limiting patterns without regard to letter
1128 case.
1129 </p>
1130 </dd>
1132 --basic-regexp
1133 </dt>
1134 <dd>
1135 <p>
1136 Consider the limiting patterns to be basic regular expressions;
1137 this is the default.
1138 </p>
1139 </dd>
1141 -E
1142 </dt>
1144 --extended-regexp
1145 </dt>
1146 <dd>
1147 <p>
1148 Consider the limiting patterns to be extended regular expressions
1149 instead of the default basic regular expressions.
1150 </p>
1151 </dd>
1153 -F
1154 </dt>
1156 --fixed-strings
1157 </dt>
1158 <dd>
1159 <p>
1160 Consider the limiting patterns to be fixed strings (don’t interpret
1161 pattern as a regular expression).
1162 </p>
1163 </dd>
1165 -P
1166 </dt>
1168 --perl-regexp
1169 </dt>
1170 <dd>
1171 <p>
1172 Consider the limiting patterns to be Perl-compatible regular
1173 expressions.
1174 </p>
1176 compile-time dependency. If Git wasn’t compiled with support for them
1177 providing this option will cause it to die.</p></div>
1178 </dd>
1180 --remove-empty
1181 </dt>
1182 <dd>
1183 <p>
1184 Stop when a given path disappears from the tree.
1185 </p>
1186 </dd>
1188 --merges
1189 </dt>
1190 <dd>
1191 <p>
1193 </p>
1194 </dd>
1196 --no-merges
1197 </dt>
1198 <dd>
1199 <p>
1200 Do not print commits with more than one parent. This is
1202 </p>
1203 </dd>
1206 </dt>
1209 </dt>
1211 --no-min-parents
1212 </dt>
1214 --no-max-parents
1215 </dt>
1216 <dd>
1217 <p>
1218 Show only commits which have at least (or at most) that many parent
1220 <code>--min-parents=2</code> is the same as <code>--merges</code>. <code>--max-parents=0</code>
1222 </p>
1223 <div class="paragraph"><p><code>--no-min-parents</code> and <code>--no-max-parents</code> reset these limits (to no limit)
1226 </dd>
1228 --first-parent
1229 </dt>
1230 <dd>
1231 <p>
1232 When finding commits to include, follow only the first
1233 parent commit upon seeing a merge commit. This option
1234 can give a better overview when viewing the evolution of
1235 a particular topic branch, because merges into a topic
1236 branch tend to be only about adjusting to updated upstream
1237 from time to time, and this option allows you to ignore
1238 the individual commits brought in to your history by such
1239 a merge.
1240 </p>
1242 to <code>first-parent</code>, see <code>--diff-merges=first-parent</code> for details.</p></div>
1243 </dd>
1245 --exclude-first-parent-only
1246 </dt>
1247 <dd>
1248 <p>
1250 the first parent commit upon seeing a merge commit.
1251 This can be used to find the set of changes in a topic branch
1252 from the point where it diverged from the remote branch, given
1253 that arbitrary merges can be valid topic branch changes.
1254 </p>
1255 </dd>
1257 --not
1258 </dt>
1259 <dd>
1260 <p>
1263 </p>
1264 </dd>
1266 --all
1267 </dt>
1268 <dd>
1269 <p>
1272 </p>
1273 </dd>
1276 </dt>
1277 <dd>
1278 <p>
1283 </p>
1284 </dd>
1287 </dt>
1288 <dd>
1289 <p>
1294 </p>
1295 </dd>
1298 </dt>
1299 <dd>
1300 <p>
1303 remote-tracking branches to ones matching given shell glob.
1304 If pattern lacks <em>?</em>, <em>*</em>, or <em>[</em>, <em>/*</em> at the end is implied.
1305 </p>
1306 </dd>
1309 </dt>
1310 <dd>
1311 <p>
1316 </p>
1317 </dd>
1320 </dt>
1321 <dd>
1322 <p>
1324 <code>--branches</code>, <code>--tags</code>, <code>--remotes</code>, or <code>--glob</code> would otherwise
1325 consider. Repetitions of this option accumulate exclusion patterns
1326 up to the next <code>--all</code>, <code>--branches</code>, <code>--tags</code>, <code>--remotes</code>, or
1328 accumulated patterns).
1329 </p>
1330 <div class="paragraph"><p>The patterns given should not begin with <code>refs/heads</code>, <code>refs/tags</code>, or
1331 <code>refs/remotes</code> when applied to <code>--branches</code>, <code>--tags</code>, or <code>--remotes</code>,
1334 explicitly.</p></div>
1335 </dd>
1337 --exclude-hidden=[fetch|receive|uploadpack]
1338 </dt>
1339 <dd>
1340 <p>
1347 </p>
1348 </dd>
1350 --reflog
1351 </dt>
1352 <dd>
1353 <p>
1354 Pretend as if all objects mentioned by reflogs are listed on the
1356 </p>
1357 </dd>
1359 --alternate-refs
1360 </dt>
1361 <dd>
1362 <p>
1363 Pretend as if all objects mentioned as ref tips of alternate
1364 repositories were listed on the command line. An alternate
1365 repository is any repository whose object directory is specified
1369 </p>
1370 </dd>
1372 --single-worktree
1373 </dt>
1374 <dd>
1375 <p>
1376 By default, all working trees will be examined by the
1377 following options when there are more than one (see
1378 <a href="git-worktree.html">git-worktree(1)</a>): <code>--all</code>, <code>--reflog</code> and
1380 This option forces them to examine the current working tree
1381 only.
1382 </p>
1383 </dd>
1385 --ignore-missing
1386 </dt>
1387 <dd>
1388 <p>
1389 Upon seeing an invalid object name in the input, pretend as if
1390 the bad input was not given.
1391 </p>
1392 </dd>
1394 --bisect
1395 </dt>
1396 <dd>
1397 <p>
1401 line.
1402 </p>
1403 </dd>
1405 --stdin
1406 </dt>
1407 <dd>
1408 <p>
1409 In addition to getting arguments from the command line, read
1410 them from standard input as well. This accepts commits and
1411 pseudo-options like <code>--all</code> and <code>--glob=</code>. When a <code>--</code> separator
1412 is seen, the following input is treated as paths and used to
1413 limit the result.
1414 </p>
1415 </dd>
1417 --cherry-mark
1418 </dt>
1419 <dd>
1420 <p>
1423 </p>
1424 </dd>
1426 --cherry-pick
1427 </dt>
1428 <dd>
1429 <p>
1430 Omit any commit that introduces the same change as
1432 commits are limited with symmetric difference.
1433 </p>
1434 <div class="paragraph"><p>For example, if you have two branches, <code>A</code> and <code>B</code>, a usual way
1435 to list all commits on only one side of them is with
1439 cherry-picked from branch A). With this option, such pairs of commits are
1440 excluded from the output.</p></div>
1441 </dd>
1443 --left-only
1444 </dt>
1446 --right-only
1447 </dt>
1448 <dd>
1449 <p>
1450 List only commits on the respective side of a symmetric difference,
1453 </p>
1454 <div class="paragraph"><p>For example, <code>--cherry-pick --right-only A...B</code> omits those
1456 <code>A</code>. In other words, this lists the <code>+</code> commits from <code>git cherry A B</code>.
1458 list.</p></div>
1459 </dd>
1461 --cherry
1462 </dt>
1463 <dd>
1464 <p>
1466 limit the output to the commits on our side and mark those that
1467 have been applied to the other side of a forked history with
1470 </p>
1471 </dd>
1473 -g
1474 </dt>
1476 --walk-reflogs
1477 </dt>
1478 <dd>
1479 <p>
1480 Instead of walking the commit ancestry chain, walk
1481 reflog entries from the most recent one to older ones.
1482 When this option is used you cannot specify commits to
1485 </p>
1486 <div class="paragraph"><p>With <code>--pretty</code> format other than <code>oneline</code> and <code>reference</code> (for obvious reasons),
1487 this causes the output to have two extra lines of information
1488 taken from the reflog. The reflog designator in the output may be shown
1491 depending on a few rules:</p></div>
1495 <li>
1496 <p>
1498 format.
1499 </p>
1500 </li>
1501 <li>
1502 <p>
1504 timestamp format.
1505 </p>
1506 </li>
1507 <li>
1508 <p>
1511 </p>
1512 </li>
1513 <li>
1514 <p>
1515 Otherwise, show the index format.
1516 </p>
1517 </li>
1518 </ol></div>
1519 </div></div>
1521 prefixed with this information on the same line.
1524 <div class="paragraph"><p>Under <code>--pretty=reference</code>, this information will not be shown at all.</p></div>
1525 </dd>
1527 --merge
1528 </dt>
1529 <dd>
1530 <p>
1531 After a failed merge, show refs that touch files having a
1532 conflict and don’t exist on all heads to merge.
1533 </p>
1534 </dd>
1536 --boundary
1537 </dt>
1538 <dd>
1539 <p>
1540 Output excluded boundary commits. Boundary commits are
1542 </p>
1543 </dd>
1544 </dl></div>
1545 </div>
1548 <div class="paragraph"><p>Sometimes you are only interested in parts of the history, for example the
1551 is how to do it, as there are various strategies to simplify the history.</p></div>
1556 </dt>
1557 <dd>
1558 <p>
1560 </p>
1561 </dd>
1563 --simplify-by-decoration
1564 </dt>
1565 <dd>
1566 <p>
1567 Commits that are referred by some branch or tag are selected.
1568 </p>
1569 </dd>
1570 </dl></div>
1571 <div class="paragraph"><p>Note that extra commits can be shown to give a meaningful history.</p></div>
1572 <div class="paragraph"><p>The following options affect the way the simplification is performed:</p></div>
1575 Default mode
1576 </dt>
1577 <dd>
1578 <p>
1579 Simplifies the history to the simplest history explaining the
1580 final state of the tree. Simplest because it prunes some side
1581 branches if the end result is the same (i.e. merging branches
1582 with the same content)
1583 </p>
1584 </dd>
1586 --show-pulls
1587 </dt>
1588 <dd>
1589 <p>
1590 Include all commits from the default mode, but also any merge
1591 commits that are not TREESAME to the first parent but are
1592 TREESAME to a later parent. This mode is helpful for showing
1593 the merge commits that "first introduced" a change to a branch.
1594 </p>
1595 </dd>
1597 --full-history
1598 </dt>
1599 <dd>
1600 <p>
1601 Same as the default mode, but does not prune some history.
1602 </p>
1603 </dd>
1605 --dense
1606 </dt>
1607 <dd>
1608 <p>
1609 Only the selected commits are shown, plus some to have a
1610 meaningful history.
1611 </p>
1612 </dd>
1614 --sparse
1615 </dt>
1616 <dd>
1617 <p>
1618 All commits in the simplified history are shown.
1619 </p>
1620 </dd>
1622 --simplify-merges
1623 </dt>
1624 <dd>
1625 <p>
1627 merges from the resulting history, as there are no selected
1628 commits contributing to this merge.
1629 </p>
1630 </dd>
1633 </dt>
1634 <dd>
1635 <p>
1641 times; if so, a commit is included if it is any of the commits
1642 given or if it is an ancestor or descendant of one of them.
1643 </p>
1644 </dd>
1645 </dl></div>
1647 <div class="paragraph"><p>Suppose you specified <code>foo</code> as the <paths>. We shall call commits
1650 <div class="paragraph"><p>In the following, we will always refer to the same example history to
1651 illustrate the differences between simplification settings. We assume
1655 <pre><code> .-A---M---N---O---P---Q
1656 / / / / / /
1657 I B C D E Y
1658 \ / / / / /
1659 `-------------' X</code></pre>
1660 </div></div>
1661 <div class="paragraph"><p>The horizontal line of history A---Q is taken to be the first parent of
1662 each merge. The commits are:</p></div>
1664 <li>
1665 <p>
1667 “asdf”, and a file <code>quux</code> exists with contents “quux”. Initial
1669 </p>
1670 </li>
1671 <li>
1672 <p>
1674 </p>
1675 </li>
1676 <li>
1677 <p>
1678 <code>B</code> contains the same change as <code>A</code>. Its merge <code>M</code> is trivial and
1679 hence TREESAME to all parents.
1680 </p>
1681 </li>
1682 <li>
1683 <p>
1684 <code>C</code> does not change <code>foo</code>, but its merge <code>N</code> changes it to “foobar”,
1685 so it is not TREESAME to any parent.
1686 </p>
1687 </li>
1688 <li>
1689 <p>
1690 <code>D</code> sets <code>foo</code> to “baz”. Its merge <code>O</code> combines the strings from
1691 <code>N</code> and <code>D</code> to “foobarbaz”; i.e., it is not TREESAME to any parent.
1692 </p>
1693 </li>
1694 <li>
1695 <p>
1696 <code>E</code> changes <code>quux</code> to “xyzzy”, and its merge <code>P</code> combines the
1697 strings to “quux xyzzy”. <code>P</code> is TREESAME to <code>O</code>, but not to <code>E</code>.
1698 </p>
1699 </li>
1700 <li>
1701 <p>
1702 <code>X</code> is an independent root commit that added a new file <code>side</code>, and <code>Y</code>
1703 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
1705 </p>
1706 </li>
1707 </ul></div>
1708 <div class="paragraph"><p><code>rev-list</code> walks backwards through history, including or excluding
1711 are available.</p></div>
1714 Default mode
1715 </dt>
1716 <dd>
1717 <p>
1718 Commits are included if they are not TREESAME to any parent
1720 commit was a merge, and it was TREESAME to one parent, follow
1721 only that parent. (Even if there are several TREESAME
1722 parents, follow only one of them.) Otherwise, follow all
1723 parents.
1724 </p>
1728 <pre><code> .-A---N---O
1729 / / /
1730 I---------D</code></pre>
1731 </div></div>
1736 <div class="paragraph"><p>Parent/child relations are only visible with <code>--parents</code>, but that does
1737 not affect the commits selected in default mode, so we have shown the
1738 parent lines.</p></div>
1739 </dd>
1741 --full-history without parent rewriting
1742 </dt>
1743 <dd>
1744 <p>
1745 This mode differs from the default in one point: always follow
1746 all parents of a merge, even if it is TREESAME to one of them.
1747 Even if more than one side of the merge has commits that are
1748 included, this does not imply that the merge itself is! In
1749 the example, we get
1750 </p>
1754 </div></div>
1755 <div class="paragraph"><p><code>M</code> was excluded because it is TREESAME to both parents. <code>E</code>,
1756 <code>C</code> and <code>B</code> were all walked, but only <code>B</code> was !TREESAME, so the others
1757 do not appear.</p></div>
1758 <div class="paragraph"><p>Note that without parent rewriting, it is not really possible to talk
1759 about the parent/child relationships between the commits, so we show
1760 them disconnected.</p></div>
1761 </dd>
1763 --full-history with parent rewriting
1764 </dt>
1765 <dd>
1766 <p>
1767 Ordinary commits are only included if they are !TREESAME
1769 </p>
1771 Along each parent, prune away commits that are not included
1772 themselves. This results in</p></div>
1775 <pre><code> .-A---M---N---O---P---Q
1776 / / / / /
1777 I B / D /
1778 \ / / / /
1779 `-------------'</code></pre>
1780 </div></div>
1781 <div class="paragraph"><p>Compare to <code>--full-history</code> without rewriting above. Note that <code>E</code>
1782 was pruned away because it is TREESAME, but the parent list of P was
1783 rewritten to contain <code>E</code>'s parent <code>I</code>. The same happened for <code>C</code> and
1785 </dd>
1786 </dl></div>
1788 affects inclusion:</p></div>
1791 --dense
1792 </dt>
1793 <dd>
1794 <p>
1795 Commits that are walked are included if they are not TREESAME
1796 to any parent.
1797 </p>
1798 </dd>
1800 --sparse
1801 </dt>
1802 <dd>
1803 <p>
1804 All commits that are walked are included.
1805 </p>
1806 <div class="paragraph"><p>Note that without <code>--full-history</code>, this still simplifies merges: if
1807 one of the parents is TREESAME, we follow only that one, so the other
1808 sides of the merge are never walked.</p></div>
1809 </dd>
1811 --simplify-merges
1812 </dt>
1813 <dd>
1814 <p>
1815 First, build a history graph in the same way that
1817 </p>
1818 <div class="paragraph"><p>Then simplify each commit <code>C</code> to its replacement <code>C'</code> in the final
1819 history according to the following rules:</p></div>
1823 <li>
1824 <p>
1826 </p>
1827 </li>
1828 <li>
1829 <p>
1830 Replace each parent <code>P</code> of <code>C'</code> with its simplification <code>P'</code>. In
1831 the process, drop parents that are ancestors of other parents or that are
1832 root commits TREESAME to an empty tree, and remove duplicates, but take care
1833 to never drop all parents that we are TREESAME to.
1834 </p>
1835 </li>
1836 <li>
1837 <p>
1840 Otherwise, it is replaced with its only parent.
1841 </p>
1842 </li>
1843 </ul></div>
1844 </div></div>
1849 <pre><code> .-A---M---N---O
1850 / / /
1851 I B D
1852 \ / /
1853 `---------'</code></pre>
1854 </div></div>
1855 <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>
1859 <li>
1860 <p>
1863 </p>
1864 </li>
1865 <li>
1866 <p>
1868 removed completely, because it had one parent and is TREESAME.
1869 </p>
1870 </li>
1871 <li>
1872 <p>
1873 <code>Q</code>'s parent list had <code>Y</code> simplified to <code>X</code>. <code>X</code> was then removed, because it
1875 parent and is TREESAME.
1876 </p>
1877 </li>
1878 </ul></div>
1879 </div></div>
1880 </dd>
1881 </dl></div>
1886 </dt>
1887 <dd>
1888 <p>
1889 Limit the displayed commits to those which are an ancestor of
1891 itself.
1892 </p>
1893 <div class="paragraph"><p>As an example use case, consider the following commit history:</p></div>
1896 <pre><code> D---E-------F
1897 / \ \
1898 B---C---G---H---I---J
1899 / \
1900 A-------K---------------L--M</code></pre>
1901 </div></div>
1902 <div class="paragraph"><p>A regular <em>D..M</em> computes the set of commits that are ancestors of <code>M</code>,
1905 that “what does <code>M</code> have that did not exist in <code>D</code>”. The result in this
1906 example would be all the commits, except <code>A</code> and <code>B</code> (and <code>D</code> itself,
1907 of course).</p></div>
1908 <div class="paragraph"><p>When we want to find out what commits in <code>M</code> are contaminated with the
1911 excluding <code>C</code> and <code>K</code>. This is exactly what the <code>--ancestry-path</code>
1915 <pre><code> E-------F
1916 \ \
1917 G---H---I---J
1918 \
1919 L--M</code></pre>
1920 </div></div>
1921 <div class="paragraph"><p>We can also use <code>--ancestry-path=D</code> instead of <code>--ancestry-path</code> which
1923 explicit.</p></div>
1924 <div class="paragraph"><p>If we instead are interested in a given topic within this range, and all
1925 commits affected by that topic, we may only want to view the subset of
1930 <pre><code> E
1931 \
1932 G---H---I---J
1933 \
1934 L--M</code></pre>
1935 </div></div>
1936 <div class="paragraph"><p>Whereas <code>--ancestry-path=K D..M</code> would result in</p></div>
1940 </div></div>
1941 </dd>
1942 </dl></div>
1943 <div class="paragraph"><p>Before discussing another option, <code>--show-pulls</code>, we need to
1944 create a new example history.</p></div>
1945 <div class="paragraph"><p>A common problem users face when looking at simplified history is that a
1946 commit they know changed a file somehow does not appear in the file’s
1947 simplified history. Let’s demonstrate a new example and show how options
1948 such as <code>--full-history</code> and <code>--simplify-merges</code> works in that case:</p></div>
1951 <pre><code> .-A---M-----C--N---O---P
1952 / / \ \ \/ / /
1953 I B \ R-'`-Z' /
1954 \ / \/ /
1955 \ / /\ /
1956 `---X--' `---Y--'</code></pre>
1957 </div></div>
1958 <div class="paragraph"><p>For this example, suppose <code>I</code> created <code>file.txt</code> which was modified by
1959 <code>A</code>, <code>B</code>, and <code>X</code> in different ways. The single-parent commits <code>C</code>, <code>Z</code>,
1960 and <code>Y</code> do not change <code>file.txt</code>. The merge commit <code>M</code> was created by
1964 the contents of <code>file.txt</code> at <code>X</code>. Hence, <code>R</code> is TREESAME to <code>X</code> but not
1966 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>.
1969 <div class="paragraph"><p>When using the default mode, <code>N</code> and <code>R</code> both have a TREESAME parent, so
1970 those edges are walked and the others are ignored. The resulting history
1971 graph is:</p></div>
1975 </div></div>
1976 <div class="paragraph"><p>When using <code>--full-history</code>, Git walks every edge. This will discover
1977 the commits <code>A</code> and <code>B</code> and the merge <code>M</code>, but also will reveal the
1978 merge commits <code>O</code> and <code>P</code>. With parent rewriting, the resulting graph is:</p></div>
1981 <pre><code> .-A---M--------N---O---P
1982 / / \ \ \/ / /
1983 I B \ R-'`--' /
1984 \ / \/ /
1985 \ / /\ /
1986 `---X--' `------'</code></pre>
1987 </div></div>
1988 <div class="paragraph"><p>Here, the merge commits <code>O</code> and <code>P</code> contribute extra noise, as they did
1991 issue in repositories using a workflow where many contributors work in
1992 parallel and merge their topic branches along a single trunk: many
1994 <div class="paragraph"><p>When using the <code>--simplify-merges</code> option, the commits <code>O</code> and <code>P</code>
1995 disappear from the results. This is because the rewritten second parents
1997 removed and then the commits look like single-parent commits that are
1999 in a history view as follows:</p></div>
2002 <pre><code> .-A---M--.
2003 / / \
2004 I B R
2005 \ / /
2006 \ / /
2007 `---X--'</code></pre>
2008 </div></div>
2010 <code>A</code>, <code>B</code>, and <code>X</code>. We also see the carefully-resolved merge <code>M</code> and the
2013 the default view. However, there are a few issues with this approach.</p></div>
2016 before returning a single result. This can make the option difficult to
2017 use for very large repositories.</p></div>
2018 <div class="paragraph"><p>The second issue is one of auditing. When many contributors are working
2019 on the same repository, it is important which merge commits introduced
2021 not likely to be the merge commit that was used to merge into an
2022 important branch. Instead, the merge <code>N</code> was used to merge <code>R</code> and <code>X</code>
2023 into the important branch. This commit may have information about why
2024 the change <code>X</code> came to override the changes from <code>A</code> and <code>B</code> in its
2025 commit message.</p></div>
2028 --show-pulls
2029 </dt>
2030 <dd>
2031 <p>
2032 In addition to the commits shown in the default history, show
2033 each merge commit that is not TREESAME to its first parent but
2034 is TREESAME to a later parent.
2035 </p>
2036 <div class="paragraph"><p>When a merge commit is included by <code>--show-pulls</code>, the merge is
2037 treated as if it "pulled" the change from another branch. When using
2039 graph is:</p></div>
2043 </div></div>
2044 <div class="paragraph"><p>Here, the merge commits <code>R</code> and <code>N</code> are included because they pulled
2047 default history.</p></div>
2048 <div class="paragraph"><p>When <code>--show-pulls</code> is paired with <code>--simplify-merges</code>, the
2049 graph includes all of the necessary information:</p></div>
2052 <pre><code> .-A---M--. N
2053 / / \ /
2054 I B R
2055 \ / /
2056 \ / /
2057 `---X--'</code></pre>
2058 </div></div>
2059 <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>
2062 branch.</p></div>
2063 </dd>
2064 </dl></div>
2065 <div class="paragraph"><p>The <code>--simplify-by-decoration</code> option allows you to view only the
2066 big picture of the topology of the history, by omitting commits
2067 that are not referenced by tags. Commits are marked as !TREESAME
2068 (in other words, kept after history simplification rules described
2070 contents of the paths given on the command line. All other
2071 commits are marked as TREESAME (subject to be simplified away).</p></div>
2072 </div>
2075 <div class="paragraph"><p>By default, the commits are shown in reverse chronological order.</p></div>
2078 --date-order
2079 </dt>
2080 <dd>
2081 <p>
2082 Show no parents before all of its children are shown, but
2083 otherwise show commits in the commit timestamp order.
2084 </p>
2085 </dd>
2087 --author-date-order
2088 </dt>
2089 <dd>
2090 <p>
2091 Show no parents before all of its children are shown, but
2092 otherwise show commits in the author timestamp order.
2093 </p>
2094 </dd>
2096 --topo-order
2097 </dt>
2098 <dd>
2099 <p>
2100 Show no parents before all of its children are shown, and
2101 avoid showing commits on multiple lines of history
2102 intermixed.
2103 </p>
2108 \ \
2110 </div></div>
2114 <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
2115 3 1); some older commits are shown before newer ones in order to
2116 avoid showing the commits from two parallel development track mixed
2117 together.</p></div>
2118 </dd>
2120 --reverse
2121 </dt>
2122 <dd>
2123 <p>
2124 Output the commits chosen to be shown (see Commit Limiting
2125 section above) in reverse order. Cannot be combined with
2127 </p>
2128 </dd>
2129 </dl></div>
2130 </div>
2133 <div class="paragraph"><p>These options are mostly targeted for packing of Git repositories.</p></div>
2136 --no-walk[=(sorted|unsorted)]
2137 </dt>
2138 <dd>
2139 <p>
2140 Only show the given commits, but do not traverse their ancestors.
2141 This has no effect if a range is specified. If the argument
2144 was given), the commits are shown in reverse chronological order
2145 by commit time.
2147 </p>
2148 </dd>
2150 --do-walk
2151 </dt>
2152 <dd>
2153 <p>
2155 </p>
2156 </dd>
2157 </dl></div>
2158 </div>
2164 </dt>
2167 </dt>
2168 <dd>
2169 <p>
2170 Pretty-print the contents of the commit logs in a given format,
2172 <em>full</em>, <em>fuller</em>, <em>reference</em>, <em>email</em>, <em>raw</em>, <em>format:<string></em>
2176 </p>
2177 <div class="paragraph"><p>See the "PRETTY FORMATS" section for some additional details for each
2178 format. When <em>=<format></em> part is omitted, it defaults to <em>medium</em>.</p></div>
2181 </dd>
2183 --abbrev-commit
2184 </dt>
2185 <dd>
2186 <p>
2187 Instead of showing the full 40-byte hexadecimal commit object
2188 name, show a prefix that names the object uniquely.
2189 "--abbrev=<n>" (which also modifies diff output, if it is displayed)
2190 option can be used to specify the minimum length of the prefix.
2191 </p>
2194 </dd>
2196 --no-abbrev-commit
2197 </dt>
2198 <dd>
2199 <p>
2200 Show the full 40-byte hexadecimal commit object name. This negates
2203 </p>
2204 </dd>
2206 --oneline
2207 </dt>
2208 <dd>
2209 <p>
2210 This is a shorthand for "--pretty=oneline --abbrev-commit"
2211 used together.
2212 </p>
2213 </dd>
2216 </dt>
2217 <dd>
2218 <p>
2219 Commit objects record the character encoding used for the log message
2220 in their encoding header; this option can be used to tell the
2221 command to re-code the commit log message in the encoding
2222 preferred by the user. For non plumbing commands this
2223 defaults to UTF-8. Note that if an object claims to be encoded
2225 verbatim; this means that invalid sequences in the original
2226 commit may be copied to the output. Likewise, if iconv(3) fails
2227 to convert the commit, we will quietly output the original
2228 object verbatim.
2229 </p>
2230 </dd>
2233 </dt>
2235 --expand-tabs
2236 </dt>
2238 --no-expand-tabs
2239 </dt>
2240 <dd>
2241 <p>
2242 Perform a tab expansion (replace each tab with enough spaces
2244 in the log message before showing it in the output.
2247 which disables tab expansion.
2248 </p>
2252 </dd>
2255 </dt>
2256 <dd>
2257 <p>
2259 commit, when showing the commit log message. This is the default
2261 there is no <code>--pretty</code>, <code>--format</code>, or <code>--oneline</code> option given
2262 on the command line.
2263 </p>
2266 environment overrides). See <a href="git-config.html">git-config(1)</a> for more details.</p></div>
2267 <div class="paragraph"><p>With an optional <em><ref></em> argument, use the ref to find the notes
2268 to display. The ref can specify the full refname when it begins
2269 with <code>refs/notes/</code>; when it begins with <code>notes/</code>, <code>refs/</code> and otherwise
2272 being displayed. Examples: "--notes=foo" will show only notes from
2275 </dd>
2277 --no-notes
2278 </dt>
2279 <dd>
2280 <p>
2282 resetting the list of notes refs from which notes are shown.
2283 Options are parsed in the order given on the command line, so e.g.
2284 "--notes --notes=foo --no-notes --notes=bar" will only show notes
2285 from "refs/notes/bar".
2286 </p>
2287 </dd>
2290 </dt>
2292 --[no-]standard-notes
2293 </dt>
2294 <dd>
2295 <p>
2296 These options are deprecated. Use the above --notes/--no-notes
2297 options instead.
2298 </p>
2299 </dd>
2301 --show-signature
2302 </dt>
2303 <dd>
2304 <p>
2305 Check the validity of a signed commit object by passing the signature
2307 </p>
2308 </dd>
2310 --relative-date
2311 </dt>
2312 <dd>
2313 <p>
2315 </p>
2316 </dd>
2319 </dt>
2320 <dd>
2321 <p>
2322 Only takes effect for dates shown in human-readable format, such
2325 are shown in the original time zone (either committer’s or
2328 </p>
2331 <div class="paragraph"><p><code>--date=relative</code> shows dates relative to the current time,
2334 <div class="paragraph"><p><code>--date=local</code> is an alias for <code>--date=default-local</code>.</p></div>
2335 <div class="paragraph"><p><code>--date=iso</code> (or <code>--date=iso8601</code>) shows timestamps in a ISO 8601-like format.
2338 <li>
2339 <p>
2341 </p>
2342 </li>
2343 <li>
2344 <p>
2345 a space between time and time zone
2346 </p>
2347 </li>
2348 <li>
2349 <p>
2350 no colon between hours and minutes of the time zone
2351 </p>
2352 </li>
2353 </ul></div>
2354 <div class="paragraph"><p><code>--date=iso-strict</code> (or <code>--date=iso8601-strict</code>) shows timestamps in strict
2356 <div class="paragraph"><p><code>--date=rfc</code> (or <code>--date=rfc2822</code>) shows timestamps in RFC 2822
2357 format, often found in email messages.</p></div>
2358 <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>
2359 <div class="paragraph"><p><code>--date=raw</code> shows the date as seconds since the epoch (1970-01-01
2362 the second two are minutes). I.e., as if the timestamp were formatted
2365 value (which is always measured in UTC), but does switch the accompanying
2366 timezone value.</p></div>
2367 <div class="paragraph"><p><code>--date=human</code> shows the timezone if the timezone does not match the
2368 current time-zone, and doesn’t print the whole date if that matches
2369 (ie skip printing year for dates that are "this year", but also skip
2370 the whole date itself if it’s in the last few days and we can just say
2371 what weekday it was). For older dates the hour and minute is also
2372 omitted.</p></div>
2373 <div class="paragraph"><p><code>--date=unix</code> shows the date as a Unix epoch timestamp (seconds since
2375 has no effect.</p></div>
2376 <div class="paragraph"><p><code>--date=format:...</code> feeds the format <code>...</code> to your system <code>strftime</code>,
2377 except for %s, %z, and %Z, which are handled internally.
2382 <div class="paragraph"><p><code>--date=default</code> is the default format, and is based on ctime(3)
2383 output. It shows a single line with three-letter day of the week,
2384 three-letter month, day-of-month, hour-minute-seconds in "HH:MM:SS"
2385 format, followed by 4-digit year, plus timezone information, unless
2387 </div></div>
2388 </dd>
2390 --parents
2391 </dt>
2392 <dd>
2393 <p>
2394 Print also the parents of the commit (in the form "commit parent…").
2396 </p>
2397 </dd>
2399 --children
2400 </dt>
2401 <dd>
2402 <p>
2403 Print also the children of the commit (in the form "commit child…").
2405 </p>
2406 </dd>
2408 --left-right
2409 </dt>
2410 <dd>
2411 <p>
2412 Mark which side of a symmetric difference a commit is reachable from.
2416 </p>
2420 <pre><code> y---b---b branch B
2421 / \ /
2422 / .
2423 / / \
2424 o---x---a---a branch A</code></pre>
2425 </div></div>
2429 <pre><code> $ git rev-list --left-right --boundary --pretty=oneline A...B
2435 -yyyyyyy... 1st on b
2437 </div></div>
2438 </dd>
2440 --graph
2441 </dt>
2442 <dd>
2443 <p>
2444 Draw a text-based graphical representation of the commit history
2445 on the left hand side of the output. This may cause extra lines
2446 to be printed in between commits, in order for the graph history
2447 to be drawn properly.
2449 </p>
2450 <div class="paragraph"><p>This enables parent rewriting, see <em>History Simplification</em> above.</p></div>
2451 <div class="paragraph"><p>This implies the <code>--topo-order</code> option by default, but the
2453 </dd>
2456 </dt>
2457 <dd>
2458 <p>
2459 When --graph is not used, all history branches are flattened
2460 which can make it hard to see that the two consecutive commits
2461 do not belong to a linear branch. This option puts a barrier
2463 is the string that will be shown instead of the default one.
2464 </p>
2465 </dd>
2466 </dl></div>
2467 </div>
2468 </div>
2469 </div>
2476 "Merge: " and the hashes of ancestral commits are printed,
2477 separated by spaces. Note that the listed commits may not
2479 have limited your view of history: for example, if you are
2480 only interested in changes related to a certain directory or
2481 file.</p></div>
2484 config option to either another format name, or a
2487 built-in formats:</p></div>
2489 <li>
2490 <p>
2492 </p>
2496 </div></div>
2498 </li>
2499 <li>
2500 <p>
2502 </p>
2507 </div></div>
2511 </div></div>
2512 </li>
2513 <li>
2514 <p>
2516 </p>
2522 </div></div>
2526 </div></div>
2530 </div></div>
2531 </li>
2532 <li>
2533 <p>
2535 </p>
2541 </div></div>
2545 </div></div>
2549 </div></div>
2550 </li>
2551 <li>
2552 <p>
2554 </p>
2562 </div></div>
2566 </div></div>
2570 </div></div>
2571 </li>
2572 <li>
2573 <p>
2575 </p>
2579 </div></div>
2580 <div class="paragraph"><p>This format is used to refer to another commit in a commit message and
2584 placeholders, its output is not affected by other options like
2586 </li>
2587 <li>
2588 <p>
2590 </p>
2597 </div></div>
2601 </div></div>
2602 </li>
2603 <li>
2604 <p>
2606 </p>
2607 <div class="paragraph"><p>Like <em>email</em>, but lines in the commit message starting with "From "
2609 confused as starting a new commit.</p></div>
2610 </li>
2611 <li>
2612 <p>
2614 </p>
2616 stored in the commit object. Notably, the hashes are
2617 displayed in full, regardless of whether --abbrev or
2619 true parent commits, without taking grafts or history
2620 simplification into account. Note that this format affects the way
2621 commits are displayed, but not the way the diff is shown e.g. with
2624 </li>
2625 <li>
2626 <p>
2628 </p>
2629 <div class="paragraph"><p>The <em>format:<format-string></em> format allows you to specify which information
2630 you want to show. It works a little bit like printf format,
2633 <div class="paragraph"><p>E.g, <em>format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"</em>
2634 would show something like this:</p></div>
2638 The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<</code></pre>
2639 </div></div>
2642 <li>
2643 <p>
2644 Placeholders that expand to a single literal character:
2645 </p>
2649 </dt>
2650 <dd>
2651 <p>
2652 newline
2653 </p>
2654 </dd>
2657 </dt>
2658 <dd>
2659 <p>
2661 </p>
2662 </dd>
2665 </dt>
2666 <dd>
2667 <p>
2669 byte with the hexadecimal digits' value (we will call this
2670 "literal formatting code" in the rest of this document).
2671 </p>
2672 </dd>
2673 </dl></div>
2674 </li>
2675 <li>
2676 <p>
2677 Placeholders that affect formatting of later placeholders:
2678 </p>
2682 </dt>
2683 <dd>
2684 <p>
2685 switch color to red
2686 </p>
2687 </dd>
2690 </dt>
2691 <dd>
2692 <p>
2693 switch color to green
2694 </p>
2695 </dd>
2698 </dt>
2699 <dd>
2700 <p>
2701 switch color to blue
2702 </p>
2703 </dd>
2706 </dt>
2707 <dd>
2708 <p>
2709 reset color
2710 </p>
2711 </dd>
2714 </dt>
2715 <dd>
2716 <p>
2717 color specification, as described under Values in the
2719 default, colors are shown only when enabled for log output
2725 not otherwise enabled (though consider just using
2727 including this format and anything else git might color).
2729 on the next placeholders until the color is switched
2730 again.
2731 </p>
2732 </dd>
2735 </dt>
2736 <dd>
2737 <p>
2739 </p>
2740 </dd>
2743 </dt>
2744 <dd>
2745 <p>
2746 switch line wrapping, like the -w option of
2748 </p>
2749 </dd>
2752 </dt>
2753 <dd>
2754 <p>
2755 make the next placeholder take at
2756 least N column widths, padding spaces on
2757 the right if necessary. Optionally
2761 N columns.
2762 Note 1: that truncating
2764 Note 2: spaces around the N and M (see below)
2765 values are optional.
2766 Note 3: Emojis and other wide characters
2767 will take two display columns, which may
2768 over-run column boundaries.
2769 Note 4: decomposed character combining marks
2770 may be misplaced at padding boundaries.
2771 </p>
2772 </dd>
2775 </dt>
2776 <dd>
2777 <p>
2778 make the next placeholder take at least until Mth
2779 display column, padding spaces on the right if necessary.
2780 Use negative M values for column positions measured
2781 from the right hand edge of the terminal window.
2782 </p>
2783 </dd>
2786 </dt>
2787 <dd>
2788 <p>
2790 but padding spaces on the left
2791 </p>
2792 </dd>
2795 </dt>
2796 <dd>
2797 <p>
2799 respectively, except that if the next
2800 placeholder takes more spaces than given and
2801 there are spaces on its left, use those
2802 spaces
2803 </p>
2804 </dd>
2807 </dt>
2808 <dd>
2809 <p>
2811 respectively, but padding both sides
2812 (i.e. the text is centered)
2813 </p>
2814 </dd>
2815 </dl></div>
2816 </li>
2817 <li>
2818 <p>
2819 Placeholders that expand to information extracted from the commit:
2820 </p>
2824 </dt>
2825 <dd>
2826 <p>
2827 commit hash
2828 </p>
2829 </dd>
2832 </dt>
2833 <dd>
2834 <p>
2835 abbreviated commit hash
2836 </p>
2837 </dd>
2840 </dt>
2841 <dd>
2842 <p>
2843 tree hash
2844 </p>
2845 </dd>
2848 </dt>
2849 <dd>
2850 <p>
2851 abbreviated tree hash
2852 </p>
2853 </dd>
2856 </dt>
2857 <dd>
2858 <p>
2859 parent hashes
2860 </p>
2861 </dd>
2864 </dt>
2865 <dd>
2866 <p>
2867 abbreviated parent hashes
2868 </p>
2869 </dd>
2872 </dt>
2873 <dd>
2874 <p>
2875 author name
2876 </p>
2877 </dd>
2880 </dt>
2881 <dd>
2882 <p>
2885 </p>
2886 </dd>
2889 </dt>
2890 <dd>
2891 <p>
2892 author email
2893 </p>
2894 </dd>
2897 </dt>
2898 <dd>
2899 <p>
2902 </p>
2903 </dd>
2906 </dt>
2907 <dd>
2908 <p>
2910 </p>
2911 </dd>
2914 </dt>
2915 <dd>
2916 <p>
2919 </p>
2920 </dd>
2923 </dt>
2924 <dd>
2925 <p>
2926 author date (format respects --date= option)
2927 </p>
2928 </dd>
2931 </dt>
2932 <dd>
2933 <p>
2934 author date, RFC2822 style
2935 </p>
2936 </dd>
2939 </dt>
2940 <dd>
2941 <p>
2942 author date, relative
2943 </p>
2944 </dd>
2947 </dt>
2948 <dd>
2949 <p>
2950 author date, UNIX timestamp
2951 </p>
2952 </dd>
2955 </dt>
2956 <dd>
2957 <p>
2958 author date, ISO 8601-like format
2959 </p>
2960 </dd>
2963 </dt>
2964 <dd>
2965 <p>
2966 author date, strict ISO 8601 format
2967 </p>
2968 </dd>
2971 </dt>
2972 <dd>
2973 <p>
2975 </p>
2976 </dd>
2979 </dt>
2980 <dd>
2981 <p>
2984 </p>
2985 </dd>
2988 </dt>
2989 <dd>
2990 <p>
2991 committer name
2992 </p>
2993 </dd>
2996 </dt>
2997 <dd>
2998 <p>
2999 committer name (respecting .mailmap, see
3001 </p>
3002 </dd>
3005 </dt>
3006 <dd>
3007 <p>
3008 committer email
3009 </p>
3010 </dd>
3013 </dt>
3014 <dd>
3015 <p>
3016 committer email (respecting .mailmap, see
3018 </p>
3019 </dd>
3022 </dt>
3023 <dd>
3024 <p>
3026 </p>
3027 </dd>
3030 </dt>
3031 <dd>
3032 <p>
3035 </p>
3036 </dd>
3039 </dt>
3040 <dd>
3041 <p>
3042 committer date (format respects --date= option)
3043 </p>
3044 </dd>
3047 </dt>
3048 <dd>
3049 <p>
3050 committer date, RFC2822 style
3051 </p>
3052 </dd>
3055 </dt>
3056 <dd>
3057 <p>
3058 committer date, relative
3059 </p>
3060 </dd>
3063 </dt>
3064 <dd>
3065 <p>
3066 committer date, UNIX timestamp
3067 </p>
3068 </dd>
3071 </dt>
3072 <dd>
3073 <p>
3074 committer date, ISO 8601-like format
3075 </p>
3076 </dd>
3079 </dt>
3080 <dd>
3081 <p>
3082 committer date, strict ISO 8601 format
3083 </p>
3084 </dd>
3087 </dt>
3088 <dd>
3089 <p>
3091 </p>
3092 </dd>
3095 </dt>
3096 <dd>
3097 <p>
3100 </p>
3101 </dd>
3104 </dt>
3105 <dd>
3106 <p>
3108 </p>
3109 </dd>
3112 </dt>
3113 <dd>
3114 <p>
3116 </p>
3117 </dd>
3120 </dt>
3121 <dd>
3122 <p>
3124 colon and zero or more comma-separated options. Option values may contain
3127 </p>
3129 <li>
3130 <p>
3131 <em>prefix=<value></em>: Shown before the list of ref names. Defaults to " <code>(</code>".
3132 </p>
3133 </li>
3134 <li>
3135 <p>
3136 <em>suffix=<value></em>: Shown after the list of ref names. Defaults to "<code>)</code>".
3137 </p>
3138 </li>
3139 <li>
3140 <p>
3142 </p>
3143 </li>
3144 <li>
3145 <p>
3147 Defaults to " <code>-></code> ".
3148 </p>
3149 </li>
3150 <li>
3151 <p>
3153 </p>
3154 </li>
3155 </ul></div>
3157 or tag annotations, and spaces as separators:</p></div>
3159 </dd>
3162 </dt>
3163 <dd>
3164 <p>
3167 zero or more comma-separated options. Descriptions can be inconsistent when
3168 tags are added or removed at the same time.
3169 </p>
3171 <li>
3172 <p>
3174 consider lightweight tags as well.
3175 </p>
3176 </li>
3177 <li>
3178 <p>
3180 (which will vary according to the number of objects in the repository with a
3182 digits as needed to form a unique object name.
3183 </p>
3184 </li>
3185 <li>
3186 <p>
3189 </p>
3190 </li>
3191 <li>
3192 <p>
3195 </p>
3196 </li>
3197 </ul></div>
3198 </dd>
3201 </dt>
3202 <dd>
3203 <p>
3204 ref name given on the command line by which the commit was reached
3206 </p>
3207 </dd>
3210 </dt>
3211 <dd>
3212 <p>
3213 encoding
3214 </p>
3215 </dd>
3218 </dt>
3219 <dd>
3220 <p>
3221 subject
3222 </p>
3223 </dd>
3226 </dt>
3227 <dd>
3228 <p>
3229 sanitized subject line, suitable for a filename
3230 </p>
3231 </dd>
3234 </dt>
3235 <dd>
3236 <p>
3237 body
3238 </p>
3239 </dd>
3242 </dt>
3243 <dd>
3244 <p>
3245 raw body (unwrapped subject and body)
3246 </p>
3247 </dd>
3250 </dt>
3251 <dd>
3252 <p>
3253 commit notes
3254 </p>
3255 </dd>
3258 </dt>
3259 <dd>
3260 <p>
3261 raw verification message from GPG for a signed commit
3262 </p>
3263 </dd>
3266 </dt>
3267 <dd>
3268 <p>
3269 show "G" for a good (valid) signature,
3270 "B" for a bad signature,
3271 "U" for a good signature with unknown validity,
3272 "X" for a good signature that has expired,
3273 "Y" for a good signature made by an expired key,
3274 "R" for a good signature made by a revoked key,
3275 "E" if the signature cannot be checked (e.g. missing key)
3276 and "N" for no signature
3277 </p>
3278 </dd>
3281 </dt>
3282 <dd>
3283 <p>
3284 show the name of the signer for a signed commit
3285 </p>
3286 </dd>
3289 </dt>
3290 <dd>
3291 <p>
3292 show the key used to sign a signed commit
3293 </p>
3294 </dd>
3297 </dt>
3298 <dd>
3299 <p>
3300 show the fingerprint of the key used to sign a signed commit
3301 </p>
3302 </dd>
3305 </dt>
3306 <dd>
3307 <p>
3308 show the fingerprint of the primary key whose subkey was used
3309 to sign a signed commit
3310 </p>
3311 </dd>
3314 </dt>
3315 <dd>
3316 <p>
3317 show the trust level for the key used to sign a signed commit
3318 </p>
3319 </dd>
3322 </dt>
3323 <dd>
3324 <p>
3326 minutes ago}</code>; the format follows the rules described for the
3330 </p>
3331 </dd>
3334 </dt>
3335 <dd>
3336 <p>
3338 portion is shortened for human readability (so
3340 </p>
3341 </dd>
3344 </dt>
3345 <dd>
3346 <p>
3347 reflog identity name
3348 </p>
3349 </dd>
3352 </dt>
3353 <dd>
3354 <p>
3355 reflog identity name (respecting .mailmap, see
3357 </p>
3358 </dd>
3361 </dt>
3362 <dd>
3363 <p>
3364 reflog identity email
3365 </p>
3366 </dd>
3369 </dt>
3370 <dd>
3371 <p>
3372 reflog identity email (respecting .mailmap, see
3374 </p>
3375 </dd>
3378 </dt>
3379 <dd>
3380 <p>
3381 reflog subject
3382 </p>
3383 </dd>
3386 </dt>
3387 <dd>
3388 <p>
3389 display the trailers of the body as interpreted by
3390 <a href="git-interpret-trailers.html">git-interpret-trailers(1)</a>. The <code>trailers</code> string may be followed by
3391 a colon and zero or more comma-separated options. If any option is provided
3392 multiple times, the last occurrence wins.
3393 </p>
3395 <li>
3396 <p>
3398 case-insensitively and trailing colon is optional. If option is
3399 given multiple times trailer lines matching any of the keys are
3401 non-trailer lines in the trailer block are hidden. If that is not
3405 </p>
3406 </li>
3407 <li>
3408 <p>
3410 block should be included.
3411 </p>
3412 </li>
3413 <li>
3414 <p>
3416 lines. When this option is not given each trailer line is
3418 the literal formatting codes described above. To use comma as
3421 shows all trailer lines whose key is "Ticket" separated by a comma
3422 and a space.
3423 </p>
3424 </li>
3425 <li>
3426 <p>
3427 <em>unfold[=<bool>]</em>: make it behave as if interpret-trailer’s <code>--unfold</code>
3428 option was given. E.g.,
3430 </p>
3431 </li>
3432 <li>
3433 <p>
3435 </p>
3436 </li>
3437 <li>
3438 <p>
3440 </p>
3441 </li>
3442 <li>
3443 <p>
3445 trailer lines. When this option is not given each trailer key-value
3446 pair is separated by ": ". Otherwise it shares the same semantics
3448 </p>
3449 </li>
3450 </ul></div>
3451 </dd>
3452 </dl></div>
3453 </li>
3454 </ul></div>
3455 </li>
3456 </ul></div>
3458 <table><tr>
3461 </td>
3464 insert an empty string unless we are traversing reflog entries (e.g., by
3465 <code>git log -g</code>). The <code>%d</code> and <code>%D</code> placeholders will use the "short"
3467 line.</td>
3468 </tr></table>
3469 </div>
3470 <div class="paragraph"><p>The boolean options accept an optional value <code>[=<bool-value>]</code>. The values
3471 <code>true</code>, <code>false</code>, <code>on</code>, <code>off</code> etc. are all accepted. See the "boolean"
3474 <div class="paragraph"><p>If you add a <code>+</code> (plus sign) after <em>%</em> of a placeholder, a line-feed
3475 is inserted immediately before the expansion if and only if the
3476 placeholder expands to a non-empty string.</p></div>
3477 <div class="paragraph"><p>If you add a <code>-</code> (minus sign) after <em>%</em> of a placeholder, all consecutive
3478 line-feeds immediately preceding the expansion are deleted if and only if the
3479 placeholder expands to an empty string.</p></div>
3481 is inserted immediately before the expansion if and only if the
3482 placeholder expands to a non-empty string.</p></div>
3484 <li>
3485 <p>
3487 </p>
3488 <div class="paragraph"><p>The <em>tformat:</em> format works exactly like <em>format:</em>, except that it
3490 other words, each commit has the message terminator character (usually a
3491 newline) appended, rather than a separator placed between entries.
3492 This means that the final entry of a single-line format will be properly
3493 terminated with a new line, just as the "oneline" format does.
3494 For example:</p></div>
3498 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
3499 4da45be
3500 7134973 -- NO NEWLINE
3503 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
3504 4da45be
3506 </div></div>
3507 <div class="paragraph"><p>In addition, any unrecognized string that has a <code>%</code> in it is interpreted
3509 equivalent:</p></div>
3514 </div></div>
3515 </li>
3516 </ul></div>
3517 </div>
3518 </div>
3522 <div class="paragraph"><p>By default, <code>git log</code> does not generate any diff output. The options
3523 below can be used to show the changes made by each commit.</p></div>
3524 <div class="paragraph"><p>Note that unless one of <code>--diff-merges</code> variants (including short
3525 <code>-m</code>, <code>-c</code>, and <code>--cc</code> options) is explicitly given, merge commits
3529 the default format.</p></div>
3532 -p
3533 </dt>
3535 -u
3536 </dt>
3538 --patch
3539 </dt>
3540 <dd>
3541 <p>
3543 </p>
3544 </dd>
3546 -s
3547 </dt>
3549 --no-patch
3550 </dt>
3551 <dd>
3552 <p>
3553 Suppress all output from the diff machinery. Useful for
3555 squelch their output, or to cancel the effect of options like
3557 </p>
3558 </dd>
3560 --diff-merges=(off|none|on|first-parent|1|separate|m|combined|c|dense-combined|cc|remerge|r)
3561 </dt>
3563 --no-diff-merges
3564 </dt>
3565 <dd>
3566 <p>
3567 Specify diff format to be used for merge commits. Default is
3570 </p>
3573 --diff-merges=(off|none)
3574 </dt>
3576 --no-diff-merges
3577 </dt>
3578 <dd>
3579 <p>
3580 Disable output of diffs for merge commits. Useful to override
3581 implied value.
3582 </p>
3583 </dd>
3585 --diff-merges=on
3586 </dt>
3588 --diff-merges=m
3589 </dt>
3591 -m
3592 </dt>
3593 <dd>
3594 <p>
3595 This option makes diff output for merge commits to be shown in
3597 is given as well. The default format could be changed using
3600 </p>
3601 </dd>
3603 --diff-merges=first-parent
3604 </dt>
3606 --diff-merges=1
3607 </dt>
3608 <dd>
3609 <p>
3610 This option makes merge commits show the full diff with
3611 respect to the first parent only.
3612 </p>
3613 </dd>
3615 --diff-merges=separate
3616 </dt>
3617 <dd>
3618 <p>
3619 This makes merge commits show the full diff with respect to
3620 each of the parents. Separate log entry and diff is generated
3621 for each parent.
3622 </p>
3623 </dd>
3625 --diff-merges=remerge
3626 </dt>
3628 --diff-merges=r
3629 </dt>
3631 --remerge-diff
3632 </dt>
3633 <dd>
3634 <p>
3635 With this option, two-parent merge commits are remerged to
3636 create a temporary tree object — potentially containing files
3637 with conflict markers and such. A diff is then shown between
3638 that temporary tree and the actual merge commit.
3639 </p>
3640 <div class="paragraph"><p>The output emitted when this option is used is subject to change, and
3641 so is its interaction with other options (unless explicitly
3642 documented).</p></div>
3643 </dd>
3645 --diff-merges=combined
3646 </dt>
3648 --diff-merges=c
3649 </dt>
3651 -c
3652 </dt>
3653 <dd>
3654 <p>
3655 With this option, diff output for a merge commit shows the
3656 differences from each of the parents to the merge result
3657 simultaneously instead of showing pairwise diff between a
3658 parent and the result one at a time. Furthermore, it lists
3661 </p>
3662 </dd>
3664 --diff-merges=dense-combined
3665 </dt>
3667 --diff-merges=cc
3668 </dt>
3670 --cc
3671 </dt>
3672 <dd>
3673 <p>
3674 With this option the output produced by
3676 uninteresting hunks whose contents in the parents have only
3677 two variants and the merge result picks one of them without
3679 </p>
3680 </dd>
3681 </dl></div>
3682 </dd>
3684 --combined-all-paths
3685 </dt>
3686 <dd>
3687 <p>
3688 This flag causes combined diffs (used for merge commits) to
3689 list the name of the file from all parents. It thus only has
3691 is likely only useful if filename changes are detected (i.e.
3692 when either rename or copy detection have been requested).
3693 </p>
3694 </dd>
3697 </dt>
3700 </dt>
3701 <dd>
3702 <p>
3704 the usual three.
3706 </p>
3707 </dd>
3710 </dt>
3711 <dd>
3712 <p>
3713 Output to a specific file instead of stdout.
3714 </p>
3715 </dd>
3718 </dt>
3721 </dt>
3724 </dt>
3725 <dd>
3726 <p>
3727 Specify the character used to indicate new, old or context
3729 ' ' respectively.
3730 </p>
3731 </dd>
3733 --raw
3734 </dt>
3735 <dd>
3736 <p>
3737 For each commit, show a summary of changes using the raw diff
3738 format. See the "RAW OUTPUT FORMAT" section of
3740 itself in raw format, which you can achieve with
3742 </p>
3743 </dd>
3745 --patch-with-raw
3746 </dt>
3747 <dd>
3748 <p>
3750 </p>
3751 </dd>
3753 -t
3754 </dt>
3755 <dd>
3756 <p>
3757 Show the tree objects in the diff output.
3758 </p>
3759 </dd>
3761 --indent-heuristic
3762 </dt>
3763 <dd>
3764 <p>
3765 Enable the heuristic that shifts diff hunk boundaries to make patches
3766 easier to read. This is the default.
3767 </p>
3768 </dd>
3770 --no-indent-heuristic
3771 </dt>
3772 <dd>
3773 <p>
3774 Disable the indent heuristic.
3775 </p>
3776 </dd>
3778 --minimal
3779 </dt>
3780 <dd>
3781 <p>
3782 Spend extra time to make sure the smallest possible
3783 diff is produced.
3784 </p>
3785 </dd>
3787 --patience
3788 </dt>
3789 <dd>
3790 <p>
3791 Generate a diff using the "patience diff" algorithm.
3792 </p>
3793 </dd>
3795 --histogram
3796 </dt>
3797 <dd>
3798 <p>
3799 Generate a diff using the "histogram diff" algorithm.
3800 </p>
3801 </dd>
3804 </dt>
3805 <dd>
3806 <p>
3807 Generate a diff using the "anchored diff" algorithm.
3808 </p>
3810 <div class="paragraph"><p>If a line exists in both the source and destination, exists only once,
3811 and starts with this text, this algorithm attempts to prevent it from
3812 appearing as a deletion or addition in the output. It uses the "patience
3814 </dd>
3816 --diff-algorithm={patience|minimal|histogram|myers}
3817 </dt>
3818 <dd>
3819 <p>
3820 Choose a diff algorithm. The variants are as follows:
3821 </p>
3827 </dt>
3828 <dd>
3829 <p>
3830 The basic greedy diff algorithm. Currently, this is the default.
3831 </p>
3832 </dd>
3835 </dt>
3836 <dd>
3837 <p>
3838 Spend extra time to make sure the smallest possible diff is
3839 produced.
3840 </p>
3841 </dd>
3844 </dt>
3845 <dd>
3846 <p>
3847 Use "patience diff" algorithm when generating patches.
3848 </p>
3849 </dd>
3852 </dt>
3853 <dd>
3854 <p>
3855 This algorithm extends the patience algorithm to "support
3856 low-occurrence common elements".
3857 </p>
3858 </dd>
3859 </dl></div>
3860 </div></div>
3861 <div class="paragraph"><p>For instance, if you configured the <code>diff.algorithm</code> variable to a
3862 non-default value and want to use the default one, then you
3864 </dd>
3867 </dt>
3868 <dd>
3869 <p>
3870 Generate a diffstat. By default, as much space as necessary
3871 will be used for the filename part, and the rest for the graph
3872 part. Maximum width defaults to terminal width, or 80 columns
3873 if not connected to a terminal, and can be overridden by
3876 of the graph part can be limited by using
3882 there are more.
3883 </p>
3884 <div class="paragraph"><p>These parameters can also be set individually with <code>--stat-width=<width></code>,
3885 <code>--stat-name-width=<name-width></code> and <code>--stat-count=<count></code>.</p></div>
3886 </dd>
3888 --compact-summary
3889 </dt>
3890 <dd>
3891 <p>
3892 Output a condensed summary of extended header information such
3895 or removing executable bit respectively) in diffstat. The
3896 information is put between the filename part and the graph
3898 </p>
3899 </dd>
3901 --numstat
3902 </dt>
3903 <dd>
3904 <p>
3906 deleted lines in decimal notation and pathname without
3907 abbreviation, to make it more machine friendly. For
3910 </p>
3911 </dd>
3913 --shortstat
3914 </dt>
3915 <dd>
3916 <p>
3918 number of modified files, as well as number of added and deleted
3919 lines.
3920 </p>
3921 </dd>
3924 </dt>
3927 </dt>
3928 <dd>
3929 <p>
3930 Output the distribution of relative amount of changes for each
3932 passing it a comma separated list of parameters.
3935 The following parameters are available:
3936 </p>
3942 </dt>
3943 <dd>
3944 <p>
3945 Compute the dirstat numbers by counting the lines that have been
3946 removed from the source, or added to the destination. This ignores
3947 the amount of pure code movements within a file. In other words,
3948 rearranging lines in a file is not counted as much as other changes.
3949 This is the default behavior when no parameter is given.
3950 </p>
3951 </dd>
3954 </dt>
3955 <dd>
3956 <p>
3957 Compute the dirstat numbers by doing the regular line-based diff
3958 analysis, and summing the removed/added line counts. (For binary
3959 files, count 64-byte chunks instead, since binary files have no
3962 lines within a file as much as other changes. The resulting output
3964 </p>
3965 </dd>
3968 </dt>
3969 <dd>
3970 <p>
3971 Compute the dirstat numbers by counting the number of files changed.
3972 Each changed file counts equally in the dirstat analysis. This is
3974 not have to look at the file contents at all.
3975 </p>
3976 </dd>
3979 </dt>
3980 <dd>
3981 <p>
3982 Count changes in a child directory for the parent directory as well.
3984 reported may exceed 100%. The default (non-cumulative) behavior can
3986 </p>
3987 </dd>
3990 </dt>
3991 <dd>
3992 <p>
3993 An integer parameter specifies a cut-off percent (3% by default).
3994 Directories contributing less than this percentage of the changes
3995 are not shown in the output.
3996 </p>
3997 </dd>
3998 </dl></div>
3999 </div></div>
4001 directories with less than 10% of the total amount of changed files,
4002 and accumulating child directory counts in the parent directories:
4004 </dd>
4006 --cumulative
4007 </dt>
4008 <dd>
4009 <p>
4010 Synonym for --dirstat=cumulative
4011 </p>
4012 </dd>
4015 </dt>
4016 <dd>
4017 <p>
4018 Synonym for --dirstat=files,param1,param2…
4019 </p>
4020 </dd>
4022 --summary
4023 </dt>
4024 <dd>
4025 <p>
4026 Output a condensed summary of extended header information
4027 such as creations, renames and mode changes.
4028 </p>
4029 </dd>
4031 --patch-with-stat
4032 </dt>
4033 <dd>
4034 <p>
4036 </p>
4037 </dd>
4039 -z
4040 </dt>
4041 <dd>
4042 <p>
4043 Separate the commits with NULs instead of with new newlines.
4044 </p>
4045 <div class="paragraph"><p>Also, when <code>--raw</code> or <code>--numstat</code> has been given, do not munge
4046 pathnames and use NULs as output field terminators.</p></div>
4047 <div class="paragraph"><p>Without this option, pathnames with "unusual" characters are quoted as
4050 </dd>
4052 --name-only
4053 </dt>
4054 <dd>
4055 <p>
4056 Show only names of changed files. The file names are often encoded in UTF-8.
4057 For more information see the discussion about encoding in the <a href="git-log.html">git-log(1)</a>
4058 manual page.
4059 </p>
4060 </dd>
4062 --name-status
4063 </dt>
4064 <dd>
4065 <p>
4066 Show only names and status of changed files. See the description
4069 </p>
4070 </dd>
4073 </dt>
4074 <dd>
4075 <p>
4076 Specify how differences in submodules are shown. When specifying
4078 shows the names of the commits at the beginning and end of the range.
4080 format is used. This format lists the commits in the range like
4081 <a href="git-submodule.html">git-submodule(1)</a> <code>summary</code> does. When <code>--submodule=diff</code>
4083 inline diff of the changes in the submodule contents between the
4085 if the config option is unset.
4086 </p>
4087 </dd>
4090 </dt>
4091 <dd>
4092 <p>
4093 Show colored diff.
4094 <code>--color</code> (i.e. without <em>=<when></em>) is the same as <code>--color=always</code>.
4095 <em><when></em> can be one of <code>always</code>, <code>never</code>, or <code>auto</code>.
4096 </p>
4097 </dd>
4099 --no-color
4100 </dt>
4101 <dd>
4102 <p>
4103 Turn off colored diff.
4105 </p>
4106 </dd>
4109 </dt>
4110 <dd>
4111 <p>
4112 Moved lines of code are colored differently.
4115 The mode must be one of:
4116 </p>
4121 no
4122 </dt>
4123 <dd>
4124 <p>
4125 Moved lines are not highlighted.
4126 </p>
4127 </dd>
4129 default
4130 </dt>
4131 <dd>
4132 <p>
4134 in the future.
4135 </p>
4136 </dd>
4138 plain
4139 </dt>
4140 <dd>
4141 <p>
4142 Any line that is added in one location and was removed
4145 that are added somewhere else in the diff. This mode picks up any
4146 moved line, but it is not very useful in a review to determine
4147 if a block of code was moved without permutation.
4148 </p>
4149 </dd>
4151 blocks
4152 </dt>
4153 <dd>
4154 <p>
4155 Blocks of moved text of at least 20 alphanumeric characters
4156 are detected greedily. The detected blocks are
4158 Adjacent blocks cannot be told apart.
4159 </p>
4160 </dd>
4162 zebra
4163 </dt>
4164 <dd>
4165 <p>
4169 the two colors indicates that a new block was detected.
4170 </p>
4171 </dd>
4173 dimmed-zebra
4174 </dt>
4175 <dd>
4176 <p>
4178 of moved code is performed. The bordering lines of two adjacent
4179 blocks are considered interesting, the rest is uninteresting.
4181 </p>
4182 </dd>
4183 </dl></div>
4184 </div></div>
4185 </dd>
4187 --no-color-moved
4188 </dt>
4189 <dd>
4190 <p>
4191 Turn off move detection. This can be used to override configuration
4193 </p>
4194 </dd>
4197 </dt>
4198 <dd>
4199 <p>
4200 This configures how whitespace is ignored when performing the
4202 These modes can be given as a comma separated list:
4203 </p>
4208 no
4209 </dt>
4210 <dd>
4211 <p>
4212 Do not ignore whitespace when performing move detection.
4213 </p>
4214 </dd>
4216 ignore-space-at-eol
4217 </dt>
4218 <dd>
4219 <p>
4220 Ignore changes in whitespace at EOL.
4221 </p>
4222 </dd>
4224 ignore-space-change
4225 </dt>
4226 <dd>
4227 <p>
4228 Ignore changes in amount of whitespace. This ignores whitespace
4229 at line end, and considers all other sequences of one or
4230 more whitespace characters to be equivalent.
4231 </p>
4232 </dd>
4234 ignore-all-space
4235 </dt>
4236 <dd>
4237 <p>
4238 Ignore whitespace when comparing lines. This ignores differences
4239 even if one line has whitespace where the other line has none.
4240 </p>
4241 </dd>
4243 allow-indentation-change
4244 </dt>
4245 <dd>
4246 <p>
4247 Initially ignore any whitespace in the move detection, then
4248 group the moved code blocks only into a block if the change in
4249 whitespace is the same per line. This is incompatible with the
4250 other modes.
4251 </p>
4252 </dd>
4253 </dl></div>
4254 </div></div>
4255 </dd>
4257 --no-color-moved-ws
4258 </dt>
4259 <dd>
4260 <p>
4261 Do not ignore whitespace when performing move detection. This can be
4262 used to override configuration settings. It is the same as
4264 </p>
4265 </dd>
4268 </dt>
4269 <dd>
4270 <p>
4272 By default, words are delimited by whitespace; see
4274 must be one of:
4275 </p>
4280 color
4281 </dt>
4282 <dd>
4283 <p>
4285 </p>
4286 </dd>
4288 plain
4289 </dt>
4290 <dd>
4291 <p>
4293 attempts to escape the delimiters if they appear in the input,
4294 so the output may be ambiguous.
4295 </p>
4296 </dd>
4298 porcelain
4299 </dt>
4300 <dd>
4301 <p>
4302 Use a special line-based format intended for script
4303 consumption. Added/removed/unchanged runs are printed in the
4305 character at the beginning of the line and extending to the
4306 end of the line. Newlines in the input are represented by a
4308 </p>
4309 </dd>
4311 none
4312 </dt>
4313 <dd>
4314 <p>
4315 Disable word diff again.
4316 </p>
4317 </dd>
4318 </dl></div>
4319 </div></div>
4321 highlight the changed parts in all modes if enabled.</p></div>
4322 </dd>
4325 </dt>
4326 <dd>
4327 <p>
4329 runs of non-whitespace to be a word. Also implies
4331 </p>
4334 considered whitespace and ignored(!) for the purposes of finding
4336 expression to make sure that it matches all non-whitespace characters.
4337 A match that contains a newline is silently truncated(!) at the
4338 newline.</p></div>
4339 <div class="paragraph"><p>For example, <code>--word-diff-regex=.</code> will treat each character as a word
4340 and, correspondingly, show differences character by character.</p></div>
4341 <div class="paragraph"><p>The regex can also be set via a diff driver or configuration option, see
4342 <a href="gitattributes.html">gitattributes(5)</a> or <a href="git-config.html">git-config(1)</a>. Giving it explicitly
4343 overrides any diff driver or configuration setting. Diff drivers
4344 override configuration settings.</p></div>
4345 </dd>
4348 </dt>
4349 <dd>
4350 <p>
4353 </p>
4354 </dd>
4356 --no-renames
4357 </dt>
4358 <dd>
4359 <p>
4360 Turn off rename detection, even when the configuration
4361 file gives the default to do so.
4362 </p>
4363 </dd>
4365 --[no-]rename-empty
4366 </dt>
4367 <dd>
4368 <p>
4369 Whether to use empty blobs as rename source.
4370 </p>
4371 </dd>
4373 --check
4374 </dt>
4375 <dd>
4376 <p>
4377 Warn if changes introduce conflict markers or whitespace errors.
4379 configuration. By default, trailing whitespaces (including
4380 lines that consist solely of whitespaces) and a space character
4381 that is immediately followed by a tab character inside the
4382 initial indent of the line are considered whitespace errors.
4383 Exits with non-zero status if problems are found. Not compatible
4384 with --exit-code.
4385 </p>
4386 </dd>
4389 </dt>
4390 <dd>
4391 <p>
4393 lines of the diff. Multiple values are separated by comma,
4396 this option is not given, and the configuration variable
4400 </p>
4401 </dd>
4403 --full-index
4404 </dt>
4405 <dd>
4406 <p>
4407 Instead of the first handful of characters, show the full
4408 pre- and post-image blob object names on the "index"
4409 line when generating patch format output.
4410 </p>
4411 </dd>
4413 --binary
4414 </dt>
4415 <dd>
4416 <p>
4420 </p>
4421 </dd>
4424 </dt>
4425 <dd>
4426 <p>
4427 Instead of showing the full 40-byte hexadecimal object
4428 name in diff-raw format output and diff-tree header
4430 hexdigits long that uniquely refers the object.
4435 </p>
4436 </dd>
4439 </dt>
4442 </dt>
4443 <dd>
4444 <p>
4445 Break complete rewrite changes into pairs of delete and
4446 create. This serves two purposes:
4447 </p>
4448 <div class="paragraph"><p>It affects the way a change that amounts to a total rewrite of a file
4449 not as a series of deletion and insertion mixed together with a very
4450 few lines that happen to match textually as the context, but as a
4451 single deletion of everything old followed by a single insertion of
4454 original should remain in the result for Git to consider it a total
4455 rewrite (i.e. otherwise the resulting patch will be a series of
4456 deletion and insertion mixed together with context lines).</p></div>
4457 <div class="paragraph"><p>When used with -M, a totally-rewritten file is also considered as the
4458 source of a rename (usually -M only considers a file that disappeared
4462 eligible for being picked up as a possible source of a rename to
4463 another file.</p></div>
4464 </dd>
4467 </dt>
4470 </dt>
4471 <dd>
4472 <p>
4473 If generating diffs, detect and report renames for each commit.
4474 For following files across renames while traversing history, see
4477 index (i.e. amount of addition/deletions compared to the
4479 delete/add pair to be a rename if more than 90% of the file
4485 </p>
4486 </dd>
4489 </dt>
4492 </dt>
4493 <dd>
4494 <p>
4497 </p>
4498 </dd>
4500 --find-copies-harder
4501 </dt>
4502 <dd>
4503 <p>
4505 if the original file of the copy was modified in the same
4506 changeset. This flag makes the command
4507 inspect unmodified files as candidates for the source of
4508 copy. This is a very expensive operation for large
4509 projects, so use it with caution. Giving more than one
4511 </p>
4512 </dd>
4514 -D
4515 </dt>
4517 --irreversible-delete
4518 </dt>
4519 <dd>
4520 <p>
4521 Omit the preimage for deletes, i.e. print only the header but not
4524 solely for people who want to just concentrate on reviewing the
4525 text after the change. In addition, the output obviously lacks
4526 enough information to apply such a patch in reverse, even manually,
4527 hence the name of the option.
4528 </p>
4529 <div class="paragraph"><p>When used together with <code>-B</code>, omit also the preimage in the deletion part
4530 of a delete/create pair.</p></div>
4531 </dd>
4534 </dt>
4535 <dd>
4536 <p>
4538 can detect subsets of renames/copies cheaply, followed by an
4539 exhaustive fallback portion that compares all remaining
4540 unpaired destinations to all relevant sources. (For renames,
4541 only remaining unpaired sources are relevant; for copies, all
4542 original sources are relevant.) For N sources and
4543 destinations, this exhaustive check is O(N^2). This option
4544 prevents the exhaustive portion of rename/copy detection from
4545 running if the number of source/destination files involved
4546 exceeds the specified number. Defaults to diff.renameLimit.
4547 Note that a value of 0 is treated as unlimited.
4548 </p>
4549 </dd>
4551 --diff-filter=[(A|C|D|M|R|T|U|X|B)…[*]]
4552 </dt>
4553 <dd>
4554 <p>
4560 Any combination of the filter characters (including none) can be used.
4562 paths are selected if there is any file that matches
4563 other criteria in the comparison; if there is no file
4564 that matches other criteria, nothing is selected.
4565 </p>
4568 <div class="paragraph"><p>Note that not all diffs can feature all types. For instance, copied and
4569 renamed entries cannot appear if detection for those types is disabled.</p></div>
4570 </dd>
4573 </dt>
4574 <dd>
4575 <p>
4576 Look for differences that change the number of occurrences of
4577 the specified string (i.e. addition/deletion) in a file.
4578 Intended for the scripter’s use.
4579 </p>
4580 <div class="paragraph"><p>It is useful when you’re looking for an exact block of code (like a
4581 struct), and want to know the history of that block since it first
4582 came into being: use the feature iteratively to feed the interesting
4584 very first version of the block.</p></div>
4586 </dd>
4589 </dt>
4590 <dd>
4591 <p>
4592 Look for differences whose patch text contains added/removed
4594 </p>
4595 <div class="paragraph"><p>To illustrate the difference between <code>-S<regex> --pickaxe-regex</code> and
4597 file:</p></div>
4601 ...
4603 </div></div>
4604 <div class="paragraph"><p>While <code>git log -G"frotz\(nitfol"</code> will show this commit, <code>git log
4606 occurrences of that string did not change).</p></div>
4607 <div class="paragraph"><p>Unless <code>--text</code> is supplied patches of binary files without a textconv
4608 filter will be ignored.</p></div>
4609 <div class="paragraph"><p>See the <em>pickaxe</em> entry in <a href="gitdiffcore.html">gitdiffcore(7)</a> for more
4610 information.</p></div>
4611 </dd>
4614 </dt>
4615 <dd>
4616 <p>
4617 Look for differences that change the number of occurrences of
4619 in that it doesn’t search for a specific string but for a specific
4620 object id.
4621 </p>
4622 <div class="paragraph"><p>The object can be a blob or a submodule commit. It implies the <code>-t</code> option in
4624 </dd>
4626 --pickaxe-all
4627 </dt>
4628 <dd>
4629 <p>
4631 changeset, not just the files that contain the change
4633 </p>
4634 </dd>
4636 --pickaxe-regex
4637 </dt>
4638 <dd>
4639 <p>
4641 expression to match.
4642 </p>
4643 </dd>
4646 </dt>
4647 <dd>
4648 <p>
4649 Control the order in which files appear in the output.
4653 </p>
4656 All files with pathnames that match the first pattern are output
4657 first, all files with pathnames that match the second pattern (but not
4658 the first) are output next, and so on.
4659 All files with pathnames that do not match any pattern are output
4660 last, as if there was an implicit match-all pattern at the end of the
4661 file.
4662 If multiple pathnames have the same rank (they match the same pattern
4663 but no earlier patterns), their output order relative to each other is
4664 the normal order.</p></div>
4669 <li>
4670 <p>
4671 Blank lines are ignored, so they can be used as separators for
4672 readability.
4673 </p>
4674 </li>
4675 <li>
4676 <p>
4677 Lines starting with a hash ("<code>#</code>") are ignored, so they can be used
4678 for comments. Add a backslash ("<code>\</code>") to the beginning of the
4679 pattern if it starts with a hash.
4680 </p>
4681 </li>
4682 <li>
4683 <p>
4684 Each other line contains a single pattern.
4685 </p>
4686 </li>
4687 </ul></div>
4688 </div></div>
4690 fnmatch(3) without the FNM_PATHNAME flag, except a pathname also
4691 matches a pattern if removing any number of the final pathname
4692 components matches the pattern. For example, the pattern "<code>foo*bar</code>"
4693 matches "<code>fooasdfbar</code>" and "<code>foo/bar/baz/asdf</code>" but not "<code>foobarx</code>".</p></div>
4694 </dd>
4697 </dt>
4700 </dt>
4701 <dd>
4702 <p>
4707 otherwise.
4708 </p>
4709 </dd>
4711 -R
4712 </dt>
4713 <dd>
4714 <p>
4715 Swap two inputs; that is, show differences from index or
4716 on-disk file to tree contents.
4717 </p>
4718 </dd>
4721 </dt>
4723 --no-relative
4724 </dt>
4725 <dd>
4726 <p>
4727 When run from a subdirectory of the project, it can be
4728 told to exclude changes outside the directory and show
4729 pathnames relative to it with this option. When you are
4730 not in a subdirectory (e.g. in a bare repository), you
4731 can name which subdirectory to make the output relative
4735 </p>
4736 </dd>
4738 -a
4739 </dt>
4741 --text
4742 </dt>
4743 <dd>
4744 <p>
4745 Treat all files as text.
4746 </p>
4747 </dd>
4749 --ignore-cr-at-eol
4750 </dt>
4751 <dd>
4752 <p>
4753 Ignore carriage-return at the end of line when doing a comparison.
4754 </p>
4755 </dd>
4757 --ignore-space-at-eol
4758 </dt>
4759 <dd>
4760 <p>
4761 Ignore changes in whitespace at EOL.
4762 </p>
4763 </dd>
4765 -b
4766 </dt>
4768 --ignore-space-change
4769 </dt>
4770 <dd>
4771 <p>
4772 Ignore changes in amount of whitespace. This ignores whitespace
4773 at line end, and considers all other sequences of one or
4774 more whitespace characters to be equivalent.
4775 </p>
4776 </dd>
4778 -w
4779 </dt>
4781 --ignore-all-space
4782 </dt>
4783 <dd>
4784 <p>
4785 Ignore whitespace when comparing lines. This ignores
4786 differences even if one line has whitespace where the other
4787 line has none.
4788 </p>
4789 </dd>
4791 --ignore-blank-lines
4792 </dt>
4793 <dd>
4794 <p>
4795 Ignore changes whose lines are all blank.
4796 </p>
4797 </dd>
4800 </dt>
4803 </dt>
4804 <dd>
4805 <p>
4807 be specified more than once.
4808 </p>
4809 </dd>
4812 </dt>
4813 <dd>
4814 <p>
4815 Show the context between diff hunks, up to the specified number
4816 of lines, thereby fusing hunks that are close to each other.
4818 is unset.
4819 </p>
4820 </dd>
4822 -W
4823 </dt>
4825 --function-context
4826 </dt>
4827 <dd>
4828 <p>
4829 Show whole function as context lines for each change.
4830 The function names are determined in the same way as
4833 </p>
4834 </dd>
4836 --ext-diff
4837 </dt>
4838 <dd>
4839 <p>
4840 Allow an external diff helper to be executed. If you set an
4843 </p>
4844 </dd>
4846 --no-ext-diff
4847 </dt>
4848 <dd>
4849 <p>
4850 Disallow external diff drivers.
4851 </p>
4852 </dd>
4854 --textconv
4855 </dt>
4857 --no-textconv
4858 </dt>
4859 <dd>
4860 <p>
4861 Allow (or disallow) external text conversion filters to be run
4863 details. Because textconv filters are typically a one-way
4864 conversion, the resulting diff is suitable for human
4865 consumption, but cannot be applied. For this reason, textconv
4867 <a href="git-log.html">git-log(1)</a>, but not for <a href="git-format-patch.html">git-format-patch(1)</a> or
4868 diff plumbing commands.
4869 </p>
4870 </dd>
4873 </dt>
4874 <dd>
4875 <p>
4878 Using "none" will consider the submodule modified when it either contains
4879 untracked or modified files or its HEAD differs from the commit recorded
4880 in the superproject and can be used to override any settings of the
4881 <em>ignore</em> option in <a href="git-config.html">git-config(1)</a> or <a href="gitmodules.html">gitmodules(5)</a>. When
4882 "untracked" is used submodules are not considered dirty when they only
4883 contain untracked content (but they are still scanned for modified
4884 content). Using "dirty" ignores all changes to the work tree of submodules,
4885 only changes to the commits stored in the superproject are shown (this was
4887 </p>
4888 </dd>
4891 </dt>
4892 <dd>
4893 <p>
4894 Show the given source prefix instead of "a/".
4895 </p>
4896 </dd>
4899 </dt>
4900 <dd>
4901 <p>
4902 Show the given destination prefix instead of "b/".
4903 </p>
4904 </dd>
4906 --no-prefix
4907 </dt>
4908 <dd>
4909 <p>
4910 Do not show any source or destination prefix.
4911 </p>
4912 </dd>
4914 --default-prefix
4915 </dt>
4916 <dd>
4917 <p>
4919 This is usually the default already, but may be used to override
4921 </p>
4922 </dd>
4925 </dt>
4926 <dd>
4927 <p>
4928 Prepend an additional prefix to every line of output.
4929 </p>
4930 </dd>
4932 --ita-invisible-in-index
4933 </dt>
4934 <dd>
4935 <p>
4936 By default entries added by "git add -N" appear as an existing
4938 This option makes the entry appear as a new file in "git diff"
4939 and non-existent in "git diff --cached". This option could be
4941 experimental and could be removed in future.
4942 </p>
4943 </dd>
4944 </dl></div>
4947 </div>
4948 </div>
4960 You can customize the creation of patch text via the
4962 (see <a href="git.html">git(1)</a>), and the <code>diff</code> attribute (see <a href="gitattributes.html">gitattributes(5)</a>).</p></div>
4963 <div class="paragraph"><p>What the -p option produces is slightly different from the traditional
4964 diff format:</p></div>
4966 <li>
4967 <p>
4968 It is preceded with a "git diff" header that looks like this:
4969 </p>
4973 </div></div>
4974 <div class="paragraph"><p>The <code>a/</code> and <code>b/</code> filenames are the same unless rename/copy is
4975 involved. Especially, even for a creation or a deletion,
4976 <code>/dev/null</code> is <em>not</em> used in place of the <code>a/</code> or <code>b/</code> filenames.</p></div>
4977 <div class="paragraph"><p>When rename/copy is involved, <code>file1</code> and <code>file2</code> show the
4978 name of the source file of the rename/copy and the name of
4979 the file that rename/copy produces, respectively.</p></div>
4980 </li>
4981 <li>
4982 <p>
4983 It is followed by one or more extended header lines:
4984 </p>
4998 </div></div>
4999 <div class="paragraph"><p>File modes are printed as 6-digit octal numbers including the file type
5000 and file permission bits.</p></div>
5001 <div class="paragraph"><p>Path names in extended headers do not include the <code>a/</code> and <code>b/</code> prefixes.</p></div>
5003 the dissimilarity index is the percentage of changed lines. It
5004 is a rounded down integer, followed by a percent sign. The
5005 similarity index value of 100% is thus reserved for two equal
5006 files, while 100% dissimilarity means that no line from the old
5007 file made it into the new one.</p></div>
5008 <div class="paragraph"><p>The index line includes the blob object names before and after the change.
5010 separate lines indicate the old and the new mode.</p></div>
5011 </li>
5012 <li>
5013 <p>
5014 Pathnames with "unusual" characters are quoted as explained for
5017 </p>
5018 </li>
5019 <li>
5020 <p>
5023 It is incorrect to apply each change to each file sequentially. For
5024 example, this patch will swap a and b:
5025 </p>
5028 <pre><code>diff --git a/a b/b
5029 rename from a
5030 rename to b
5031 diff --git a/b b/a
5032 rename from b
5033 rename to a</code></pre>
5034 </div></div>
5035 </li>
5036 <li>
5037 <p>
5038 Hunk headers mention the name of the function to which the hunk
5039 applies. See "Defining a custom hunk-header" in
5041 specific languages.
5042 </p>
5043 </li>
5044 </ol></div>
5045 </div>
5046 </div>
5050 <div class="paragraph"><p>Any diff-generating command can take the <code>-c</code> or <code>--cc</code> option to
5055 diffs in specific format.</p></div>
5059 <pre><code>diff --combined describe.c
5060 index fabadb8,cc95eb0..4866510
5061 --- a/describe.c
5062 +++ b/describe.c
5065 }
5067 - static void describe(char *arg)
5068 -static void describe(struct commit *cmit, int last_one)
5069 ++static void describe(char *arg, int last_one)
5070 {
5071 + unsigned char sha1[20];
5072 + struct commit *cmit;
5073 struct commit_list *list;
5074 static int initialized = 0;
5075 struct commit_name *n;
5078 + usage(describe_usage);
5079 + cmit = lookup_commit_reference(sha1);
5080 + if (!cmit)
5081 + usage(describe_usage);
5082 +
5083 if (!initialized) {
5084 initialized = 1;
5085 for_each_ref(get_name);</code></pre>
5086 </div></div>
5088 <li>
5089 <p>
5090 It is preceded with a "git diff" header, that looks like
5092 </p>
5096 </div></div>
5101 </div></div>
5102 </li>
5103 <li>
5104 <p>
5105 It is followed by one or more extended header lines
5106 (this example shows a merge with two parents):
5107 </p>
5114 </div></div>
5115 <div class="paragraph"><p>The <code>mode <mode>,<mode>..<mode></code> line appears only if at least one of
5117 information about detected contents movement (renames and
5118 copying detection) are designed to work with diff of two
5120 </li>
5121 <li>
5122 <p>
5123 It is followed by two-line from-file/to-file header
5124 </p>
5127 <pre><code>--- a/file
5128 +++ b/file</code></pre>
5129 </div></div>
5132 files.</p></div>
5133 <div class="paragraph"><p>However, if the --combined-all-paths option is provided, instead of a
5134 two-line from-file/to-file you get a N+1 line from-file/to-file header,
5135 where N is the number of parents in the merge commit</p></div>
5138 <pre><code>--- a/file
5139 --- a/file
5140 --- a/file
5141 +++ b/file</code></pre>
5142 </div></div>
5144 active, to allow you to see the original name of the file in different
5145 parents.</p></div>
5146 </li>
5147 <li>
5148 <p>
5149 Chunk header format is modified to prevent people from
5151 was created for review of merge commit changes, and was not
5152 meant to be applied. The change is similar to the change in the
5154 </p>
5157 <pre><code>@@@ <from-file-range> <from-file-range> <to-file-range> @@@</code></pre>
5158 </div></div>
5159 <div class="paragraph"><p>There are (number of parents + 1) <code>@</code> characters in the chunk
5160 header for combined diff format.</p></div>
5161 </li>
5162 </ol></div>
5164 files A and B with a single column that has <code>-</code> (minus — appears in A but removed in B), <code>+</code> (plus — missing in A but
5166 compares two or more files file1, file2,… with one file X, and
5167 shows how X differs from each of fileN. One column for each of
5168 fileN is prepended to the output line to note how X’s line is
5169 different from it.</p></div>
5170 <div class="paragraph"><p>A <code>-</code> character in the column N means that the line appears in
5172 in the column N means that the line appears in the result,
5173 and fileN does not have that line (in other words, the line was
5174 added, from the point of view of that parent).</p></div>
5178 in either file1 or file2). Also eight other lines are the same
5180 <div class="paragraph"><p>When shown by <code>git diff-tree -c</code>, it compares the parents of a
5181 merge commit with the merge result (i.e. file1..fileN are the
5183 two unresolved merge parents with the working tree file
5186 </div>
5187 </div>
5194 </dt>
5195 <dd>
5196 <p>
5197 Show the whole commit history, but skip any merges
5198 </p>
5199 </dd>
5202 </dt>
5203 <dd>
5204 <p>
5207 </p>
5208 </dd>
5211 </dt>
5212 <dd>
5213 <p>
5217 </p>
5218 </dd>
5221 </dt>
5222 <dd>
5223 <p>
5224 Show the commits that are in the "test" branch but not yet
5225 in the "release" branch, along with the list of paths
5226 each commit modifies.
5227 </p>
5228 </dd>
5231 </dt>
5232 <dd>
5233 <p>
5235 those commits that occurred before the file was given its
5236 present name.
5237 </p>
5238 </dd>
5241 </dt>
5242 <dd>
5243 <p>
5244 Shows all commits that are in any of local branches but not in
5246 origin doesn’t).
5247 </p>
5248 </dd>
5251 </dt>
5252 <dd>
5253 <p>
5254 Shows all commits that are in local master but not in any remote
5255 repository master branches.
5256 </p>
5257 </dd>
5260 </dt>
5261 <dd>
5262 <p>
5263 Shows the history including change diffs, but only from the
5265 branches, and showing full diffs of changes introduced by the merges.
5266 This makes sense only when following a strict policy of merging all
5267 topic branches when staying on a single integration branch.
5268 </p>
5269 </dd>
5272 </dt>
5273 <dd>
5274 <p>
5276 over time.
5277 </p>
5278 </dd>
5281 </dt>
5282 <dd>
5283 <p>
5284 Limits the number of commits to show to 3.
5285 </p>
5286 </dd>
5287 </dl></div>
5288 </div>
5289 </div>
5295 <li>
5296 <p>
5297 The contents of the blob objects are uninterpreted sequences
5298 of bytes. There is no encoding translation at the core
5299 level.
5300 </p>
5301 </li>
5302 <li>
5303 <p>
5304 Path names are encoded in UTF-8 normalization form C. This
5305 applies to tree objects, the index file, ref names, as well as
5306 path names in command line arguments, environment variables
5308 <a href="gitignore.html">gitignore(5)</a>, <a href="gitattributes.html">gitattributes(5)</a> and
5310 </p>
5312 sequences of non-NUL bytes, there are no path name encoding
5313 conversions (except on Mac and Windows). Therefore, using
5314 non-ASCII path names will mostly work even on platforms and file
5315 systems that use legacy extended ASCII encodings. However,
5316 repositories created on such systems will not work properly on
5317 UTF-8-based systems (e.g. Linux, Mac, Windows) and vice versa.
5318 Additionally, many Git-based tools simply assume path names to
5320 </li>
5321 <li>
5322 <p>
5323 Commit log messages are typically encoded in UTF-8, but other
5324 extended ASCII encodings are also supported. This includes
5326 EBCDIC and CJK multi-byte encodings (GBK, Shift-JIS, Big5,
5327 EUC-x, CP9xx etc.).
5328 </p>
5329 </li>
5330 </ul></div>
5332 in UTF-8, both the core and Git Porcelain are designed not to
5333 force UTF-8 on projects. If all participants of a particular
5334 project find it more convenient to use legacy encodings, Git
5335 does not forbid it. However, there are a few things to keep in
5336 mind.</p></div>
5338 <li>
5339 <p>
5341 a warning if the commit log message given to it does not look
5342 like a valid UTF-8 string, unless you explicitly say your
5343 project uses a legacy encoding. The way to say this is to
5345 </p>
5348 <pre><code>[i18n]
5350 </div></div>
5353 help other people who look at them later. Lack of this header
5355 </li>
5356 <li>
5357 <p>
5360 log message into UTF-8 unless otherwise specified. You can
5361 specify the desired output encoding with
5363 </p>
5366 <pre><code>[i18n]
5368 </div></div>
5371 </li>
5372 </ol></div>
5374 message when a commit is made to force UTF-8 at the commit
5375 object level, because re-coding to UTF-8 is not necessarily a
5376 reversible operation.</p></div>
5377 </div>
5378 </div>
5382 <div class="paragraph"><p>See <a href="git-config.html">git-config(1)</a> for core variables and <a href="git-diff.html">git-diff(1)</a>
5383 for settings related to diff generation.</p></div>
5386 format.pretty
5387 </dt>
5388 <dd>
5389 <p>
5392 </p>
5393 </dd>
5395 i18n.logOutputEncoding
5396 </dt>
5397 <dd>
5398 <p>
5401 otherwise.
5402 </p>
5403 </dd>
5404 </dl></div>
5405 <div class="paragraph"><p>Everything above this line in this section isn’t included from the
5410 log.abbrevCommit
5411 </dt>
5412 <dd>
5413 <p>
5414 If true, makes <a href="git-log.html">git-log(1)</a>, <a href="git-show.html">git-show(1)</a>, and
5415 <a href="git-whatchanged.html">git-whatchanged(1)</a> assume <code>--abbrev-commit</code>. You may
5417 </p>
5418 </dd>
5420 log.date
5421 </dt>
5422 <dd>
5423 <p>
5427 </p>
5430 be used.</p></div>
5431 </dd>
5433 log.decorate
5434 </dt>
5435 <dd>
5436 <p>
5437 Print out the ref names of any commits that are shown by the log
5440 specified, the full ref name (including prefix) will be printed.
5445 </p>
5446 </dd>
5448 log.initialDecorationSet
5449 </dt>
5450 <dd>
5451 <p>
5454 decorations.
5455 </p>
5456 </dd>
5458 log.excludeDecoration
5459 </dt>
5460 <dd>
5461 <p>
5462 Exclude the specified patterns from the log decorations. This is
5465 option.
5466 </p>
5467 </dd>
5469 log.diffMerges
5470 </dt>
5471 <dd>
5472 <p>
5476 </p>
5477 </dd>
5479 log.follow
5480 </dt>
5481 <dd>
5482 <p>
5483 If <code>true</code>, <code>git log</code> will act as if the <code>--follow</code> option was used when
5485 i.e. it cannot be used to follow multiple files and does not work well
5486 on non-linear history.
5487 </p>
5488 </dd>
5490 log.graphColors
5491 </dt>
5492 <dd>
5493 <p>
5494 A list of colors, separated by commas, that can be used to draw
5496 </p>
5497 </dd>
5499 log.showRoot
5500 </dt>
5501 <dd>
5502 <p>
5503 If true, the initial commit will be shown as a big creation event.
5504 This is equivalent to a diff against an empty tree.
5505 Tools like <a href="git-log.html">git-log(1)</a> or <a href="git-whatchanged.html">git-whatchanged(1)</a>, which
5506 normally hide the root commit will now show it. True by default.
5507 </p>
5508 </dd>
5510 log.showSignature
5511 </dt>
5512 <dd>
5513 <p>
5514 If true, makes <a href="git-log.html">git-log(1)</a>, <a href="git-show.html">git-show(1)</a>, and
5516 </p>
5517 </dd>
5519 log.mailmap
5520 </dt>
5521 <dd>
5522 <p>
5523 If true, makes <a href="git-log.html">git-log(1)</a>, <a href="git-show.html">git-show(1)</a>, and
5524 <a href="git-whatchanged.html">git-whatchanged(1)</a> assume <code>--use-mailmap</code>, otherwise
5526 </p>
5527 </dd>
5529 notes.mergeStrategy
5530 </dt>
5531 <dd>
5532 <p>
5533 Which merge strategy to choose by default when resolving notes
5534 conflicts. Must be one of <code>manual</code>, <code>ours</code>, <code>theirs</code>, <code>union</code>, or
5537 </p>
5538 <div class="paragraph"><p>This setting can be overridden by passing the <code>--strategy</code> option to
5540 </dd>
5543 </dt>
5544 <dd>
5545 <p>
5546 Which merge strategy to choose when doing a notes merge into
5550 </p>
5551 </dd>
5553 notes.displayRef
5554 </dt>
5555 <dd>
5556 <p>
5557 Which ref (or refs, if a glob or specified more than once), in
5561 </p>
5562 <div class="paragraph"><p>This setting can be overridden with the <code>GIT_NOTES_DISPLAY_REF</code>
5563 environment variable, which must be a colon separated list of refs or
5564 globs.</p></div>
5566 but a glob that does not match any refs is silently ignored.</p></div>
5567 <div class="paragraph"><p>This setting can be disabled by the <code>--no-notes</code> option to the <em>git
5569 those commands.</p></div>
5571 GIT_NOTES_REF) is also implicitly added to the list of refs to be
5572 displayed.</p></div>
5573 </dd>
5576 </dt>
5577 <dd>
5578 <p>
5581 notes from the original to the rewritten commit. Defaults to
5583 </p>
5584 <div class="paragraph"><p>This setting can be overridden with the <code>GIT_NOTES_REWRITE_REF</code>
5585 environment variable, which must be a colon separated list of refs or
5586 globs.</p></div>
5587 </dd>
5589 notes.rewriteMode
5590 </dt>
5591 <dd>
5592 <p>
5593 When copying notes during a rewrite (see the
5594 "notes.rewrite.<command>" option), determines what to do if
5595 the target commit already has a note. Must be one of
5596 <code>overwrite</code>, <code>concatenate</code>, <code>cat_sort_uniq</code>, or <code>ignore</code>.
5598 </p>
5599 <div class="paragraph"><p>This setting can be overridden with the <code>GIT_NOTES_REWRITE_MODE</code>
5600 environment variable.</p></div>
5601 </dd>
5603 notes.rewriteRef
5604 </dt>
5605 <dd>
5606 <p>
5607 When copying notes during a rewrite, specifies the (fully
5608 qualified) ref whose notes should be copied. May be a glob,
5609 in which case notes in all matching refs will be copied. You
5610 may also specify this configuration several times.
5611 </p>
5614 rewriting for the default commit notes.</p></div>
5615 <div class="paragraph"><p>Can be overridden with the <code>GIT_NOTES_REWRITE_REF</code> environment variable.
5616 See <code>notes.rewrite.<command></code> above for a further description of its format.</p></div>
5617 </dd>
5618 </dl></div>
5619 </div>
5620 </div>
5625 </div>
5626 </div>
5627 </div>
5631 Last updated
5633 </div>
5634 </div>
5635 </body>
5636 </html>