1 <?xml version=
"1.0" encoding=
"UTF-8"?>
2 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.1//EN"
3 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
4 <html xmlns=
"http://www.w3.org/1999/xhtml" xml:
lang=
"en">
6 <meta http-equiv=
"Content-Type" content=
"application/xhtml+xml; charset=UTF-8" />
7 <meta name=
"generator" content=
"AsciiDoc 10.2.0" />
8 <title>git-show(
1)
</title>
9 <style type=
"text/css">
10 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
14 font-family: Georgia,serif;
18 h1, h2, h3, h4, h5, h6,
19 div.title, caption.title,
20 thead, p.table.header,
22 #author, #revnumber, #revdate, #revremark,
24 font-family: Arial,Helvetica,sans-serif;
28 margin:
1em
5%
1em
5%;
33 text-decoration: underline;
49 h1, h2, h3, h4, h5, h6 {
57 border-bottom:
2px solid silver;
77 border:
1px solid silver;
88 ul
> li { color: #aaa; }
89 ul
> li
> * { color: black; }
91 .monospaced, code, pre {
92 font-family:
"Courier New", Courier, monospace;
99 white-space: pre-wrap;
109 #revnumber, #revdate, #revremark {
114 border-top:
2px solid silver;
120 padding-bottom:
0.5em;
124 padding-bottom:
0.5em;
129 margin-bottom:
1.5em;
131 div.imageblock, div.exampleblock, div.verseblock,
132 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
133 div.admonitionblock {
135 margin-bottom:
1.5em;
137 div.admonitionblock {
139 margin-bottom:
2.0em;
144 div.content { /* Block element content. */
148 /* Block element titles. */
149 div.title, caption.title {
154 margin-bottom:
0.5em;
160 td div.title:first-child {
163 div.content div.title:first-child {
166 div.content + div.title {
170 div.sidebarblock
> div.content {
172 border:
1px solid #dddddd;
173 border-left:
4px solid #f0f0f0;
177 div.listingblock
> div.content {
178 border:
1px solid #dddddd;
179 border-left:
5px solid #f0f0f0;
184 div.quoteblock, div.verseblock {
188 border-left:
5px solid #f0f0f0;
192 div.quoteblock
> div.attribution {
197 div.verseblock
> pre.content {
198 font-family: inherit;
201 div.verseblock
> div.attribution {
205 /* DEPRECATED: Pre version
8.2.7 verse style literal block. */
206 div.verseblock + div.attribution {
210 div.admonitionblock .icon {
214 text-decoration: underline;
216 padding-right:
0.5em;
218 div.admonitionblock td.content {
220 border-left:
3px solid #dddddd;
223 div.exampleblock
> div.content {
224 border-left:
3px solid #dddddd;
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; }
234 margin-bottom:
0.8em;
247 list-style-position: outside;
250 list-style-type: decimal;
253 list-style-type: lower-alpha;
256 list-style-type: upper-alpha;
259 list-style-type: lower-roman;
262 list-style-type: upper-roman;
265 div.compact ul, div.compact ol,
266 div.compact p, div.compact p,
267 div.compact div, div.compact div {
269 margin-bottom:
0.1em;
281 margin-bottom:
0.8em;
284 padding-bottom:
15px;
286 dt.hdlist1.strong, td.hdlist1.strong {
292 padding-right:
0.8em;
298 div.hdlist.compact tr {
307 .footnote, .footnoteref {
311 span.footnote, span.footnoteref {
312 vertical-align: super;
316 margin:
20px
0 20px
0;
320 #footnotes div.footnote {
326 border-top:
1px solid silver;
335 padding-right:
0.5em;
336 padding-bottom:
0.3em;
344 #footer-badges { display: none; }
348 margin-bottom:
2.5em;
356 margin-bottom:
0.1em;
359 div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
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; }
427 margin-bottom:
1.5em;
429 div.tableblock
> table {
430 border:
3px solid #
527bbd;
432 thead, p.table.header {
439 /* Because the table frame attribute is overridden by CSS in most browsers. */
440 div.tableblock
> table[
frame=
"void"] {
443 div.tableblock
> table[
frame=
"hsides"] {
444 border-left-style: none;
445 border-right-style: none;
447 div.tableblock
> table[
frame=
"vsides"] {
448 border-top-style: none;
449 border-bottom-style: none;
460 margin-bottom:
1.5em;
462 thead, p.tableblock.header {
473 border-color: #
527bbd;
474 border-collapse: collapse;
476 th.tableblock, td.tableblock {
480 border-color: #
527bbd;
483 table.tableblock.frame-topbot {
484 border-left-style: hidden;
485 border-right-style: hidden;
487 table.tableblock.frame-sides {
488 border-top-style: hidden;
489 border-bottom-style: hidden;
491 table.tableblock.frame-none {
492 border-style: hidden;
495 th.tableblock.halign-left, td.tableblock.halign-left {
498 th.tableblock.halign-center, td.tableblock.halign-center {
501 th.tableblock.halign-right, td.tableblock.halign-right {
505 th.tableblock.valign-top, td.tableblock.valign-top {
508 th.tableblock.valign-middle, td.tableblock.valign-middle {
509 vertical-align: middle;
511 th.tableblock.valign-bottom, td.tableblock.valign-bottom {
512 vertical-align: bottom;
523 padding-bottom:
0.5em;
524 border-top:
2px solid silver;
525 border-bottom:
2px solid silver;
530 body.manpage div.sectionbody {
535 body.manpage div#toc { display: none; }
540 <script type=
"text/javascript">
542 var asciidoc = { // Namespace.
544 /////////////////////////////////////////////////////////////////////
545 // Table Of Contents generator
546 /////////////////////////////////////////////////////////////////////
548 /* Author: Mihai Bazon, September
2002
549 * http://students.infoiasi.ro/~mishoo
551 * Table Of Content generator
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.
558 /* modified by Troy D. Hanson, September
2006. License: GPL */
559 /* modified by Stuart Rackham,
2006,
2009. License: GPL */
562 toc: function (toclevels) {
564 function getText(el) {
566 for (var i = el.firstChild; i != null; i = i.nextSibling) {
567 if (i.nodeType ==
3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
569 else if (i.firstChild != null)
575 function TocEntry(el, text, toclevel) {
578 this.toclevel = toclevel;
581 function tocEntries(el, toclevels) {
582 var result = new Array;
583 var re = new RegExp('[hH]([
1-'+(toclevels+
1)+'])');
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
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);
591 if (mo && (i.getAttribute(
"class") || i.getAttribute(
"className")) !=
"float") {
592 result[result.length] = new TocEntry(i, getText(i), mo[
1]-
1);
602 var toc = document.getElementById(
"toc");
607 // Delete existing TOC entries in case we're reloading the TOC.
608 var tocEntriesToRemove = [];
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);
617 for (i =
0; i < tocEntriesToRemove.length; i++) {
618 toc.removeChild(tocEntriesToRemove[i]);
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");
632 div.className =
"toclevel" + entry.toclevel;
633 toc.appendChild(div);
635 if (entries.length ==
0)
636 toc.parentNode.removeChild(toc);
640 /////////////////////////////////////////////////////////////////////
641 // Footnotes generator
642 /////////////////////////////////////////////////////////////////////
644 /* Based on footnote generation code from:
645 * http://www.brandspankingnew.net/archive/
2005/
07/format_footnote.html
648 footnotes: function () {
649 // Delete existing footnote entries in case we're reloading the footnodes.
651 var noteholder = document.getElementById(
"footnotes");
655 var entriesToRemove = [];
656 for (i =
0; i < noteholder.childNodes.length; i++) {
657 var entry = noteholder.childNodes[i];
658 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute(
"class") ==
"footnote")
659 entriesToRemove.push(entry);
661 for (i =
0; i < entriesToRemove.length; i++) {
662 noteholder.removeChild(entriesToRemove[i]);
665 // Rebuild footnote entries.
666 var cont = document.getElementById(
"content");
667 var spans = cont.getElementsByTagName(
"span");
670 for (i=
0; i
<spans.length; i++) {
671 if (spans[i].className ==
"footnote") {
673 var note = spans[i].getAttribute(
"data-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];
679 "[<a id='_footnoteref_" + n +
"' href='#_footnote_" + n +
680 "' title='View footnote' class='footnote'>" + n +
"</a>]";
681 spans[i].setAttribute(
"data-note", note);
683 noteholder.innerHTML +=
684 "<div class='footnote' id='_footnote_" + n +
"'>" +
685 "<a href='#_footnoteref_" + n +
"' title='Return to text'>" +
686 n +
"</a>. " + note +
"</div>";
687 var id =spans[i].getAttribute(
"id");
688 if (id != null) refs[
"#"+id] = n;
692 noteholder.parentNode.removeChild(noteholder);
694 // Process footnoterefs.
695 for (i=
0; i
<spans.length; i++) {
696 if (spans[i].className ==
"footnoteref") {
697 var href = spans[i].getElementsByTagName(
"a")[
0].getAttribute(
"href");
698 href = href.match(/#.*/)[
0]; // Because IE return full URL.
701 "[<a href='#_footnote_" + n +
702 "' title='View footnote' class='footnote'>" + n +
"</a>]";
708 install: function(toclevels) {
711 function reinstall() {
712 asciidoc.footnotes();
714 asciidoc.toc(toclevels);
718 function reinstallAndRemoveTimer() {
719 clearInterval(timerId);
723 timerId = setInterval(reinstall,
500);
724 if (document.addEventListener)
725 document.addEventListener(
"DOMContentLoaded", reinstallAndRemoveTimer, false);
727 window.onload = reinstallAndRemoveTimer;
735 <body class=
"manpage">
738 git-show(
1) Manual Page
741 <div class=
"sectionbody">
743 Show various types of objects
749 <h2 id=
"_synopsis">SYNOPSIS
</h2>
750 <div class=
"sectionbody">
751 <div class=
"verseblock">
752 <pre class=
"content"><em>git show
</em> [
<options
>] [
<object
>…]
</pre>
753 <div class=
"attribution">
758 <h2 id=
"_description">DESCRIPTION
</h2>
759 <div class=
"sectionbody">
760 <div class=
"paragraph"><p>Shows one or more objects (blobs, trees, tags and commits).
</p></div>
761 <div class=
"paragraph"><p>For commits it shows the log message and textual diff. It also
762 presents the merge commit in a special format as produced by
763 <em>git diff-tree --cc
</em>.
</p></div>
764 <div class=
"paragraph"><p>For tags, it shows the tag message and the referenced objects.
</p></div>
765 <div class=
"paragraph"><p>For trees, it shows the names (equivalent to
<em>git ls-tree
</em>
766 with --name-only).
</p></div>
767 <div class=
"paragraph"><p>For plain blobs, it shows the plain contents.
</p></div>
768 <div class=
"paragraph"><p>The command takes options applicable to the
<em>git diff-tree
</em> command to
769 control how the changes the commit introduces are shown.
</p></div>
770 <div class=
"paragraph"><p>This manual page describes only the most frequently used options.
</p></div>
774 <h2 id=
"_options">OPTIONS
</h2>
775 <div class=
"sectionbody">
776 <div class=
"dlist"><dl>
778 <object
>…
782 The names of objects to show (defaults to
<em>HEAD
</em>).
783 For a more complete list of ways to spell object names, see
784 "SPECIFYING REVISIONS" section in
<a href=
"gitrevisions.html">gitrevisions(
7)
</a>.
788 --pretty[=
<format
>]
791 --format=
<format
>
795 Pretty-print the contents of the commit logs in a given format,
796 where
<em><format
></em> can be one of
<em>oneline
</em>,
<em>short
</em>,
<em>medium
</em>,
797 <em>full
</em>,
<em>fuller
</em>,
<em>reference
</em>,
<em>email
</em>,
<em>raw
</em>,
<em>format:
<string
></em>
798 and
<em>tformat:
<string
></em>. When
<em><format
></em> is none of the above,
799 and has
<em>%placeholder
</em> in it, it acts as if
800 <em>--pretty=tformat:
<format
></em> were given.
802 <div class=
"paragraph"><p>See the
"PRETTY FORMATS" section for some additional details for each
803 format. When
<em>=
<format
></em> part is omitted, it defaults to
<em>medium
</em>.
</p></div>
804 <div class=
"paragraph"><p>Note: you can specify the default pretty format in the repository
805 configuration (see
<a href=
"git-config.html">git-config(
1)
</a>).
</p></div>
812 Instead of showing the full
40-byte hexadecimal commit object
813 name, show a prefix that names the object uniquely.
814 "--abbrev=<n>" (which also modifies diff output, if it is displayed)
815 option can be used to specify the minimum length of the prefix.
817 <div class=
"paragraph"><p>This should make
"--pretty=oneline" a whole lot more readable for
818 people using
80-column terminals.
</p></div>
825 Show the full
40-byte hexadecimal commit object name. This negates
826 <code>--abbrev-commit
</code>, either explicit or implied by other options such
827 as
"--oneline". It also overrides the
<code>log.abbrevCommit
</code> variable.
835 This is a shorthand for
"--pretty=oneline --abbrev-commit"
840 --encoding=
<encoding
>
844 Commit objects record the character encoding used for the log message
845 in their encoding header; this option can be used to tell the
846 command to re-code the commit log message in the encoding
847 preferred by the user. For non plumbing commands this
848 defaults to UTF-
8. Note that if an object claims to be encoded
849 in
<code>X
</code> and we are outputting in
<code>X
</code>, we will output the object
850 verbatim; this means that invalid sequences in the original
851 commit may be copied to the output. Likewise, if iconv(
3) fails
852 to convert the commit, we will quietly output the original
857 --expand-tabs=
<n
>
867 Perform a tab expansion (replace each tab with enough spaces
868 to fill to the next display column that is multiple of
<em><n
></em>)
869 in the log message before showing it in the output.
870 <code>--expand-tabs
</code> is a short-hand for
<code>--expand-tabs=
8</code>, and
871 <code>--no-expand-tabs
</code> is a short-hand for
<code>--expand-tabs=
0</code>,
872 which disables tab expansion.
874 <div class=
"paragraph"><p>By default, tabs are expanded in pretty formats that indent the log
875 message by
4 spaces (i.e.
<em>medium
</em>, which is the default,
<em>full
</em>,
876 and
<em>fuller
</em>).
</p></div>
879 --notes[=
<ref
>]
883 Show the notes (see
<a href=
"git-notes.html">git-notes(
1)
</a>) that annotate the
884 commit, when showing the commit log message. This is the default
885 for
<code>git log
</code>,
<code>git show
</code> and
<code>git whatchanged
</code> commands when
886 there is no
<code>--pretty
</code>,
<code>--format
</code>, or
<code>--oneline
</code> option given
889 <div class=
"paragraph"><p>By default, the notes shown are from the notes refs listed in the
890 <code>core.notesRef
</code> and
<code>notes.displayRef
</code> variables (or corresponding
891 environment overrides). See
<a href=
"git-config.html">git-config(
1)
</a> for more details.
</p></div>
892 <div class=
"paragraph"><p>With an optional
<em><ref
></em> argument, use the ref to find the notes
893 to display. The ref can specify the full refname when it begins
894 with
<code>refs/notes/
</code>; when it begins with
<code>notes/
</code>,
<code>refs/
</code> and otherwise
895 <code>refs/notes/
</code> is prefixed to form a full name of the ref.
</p></div>
896 <div class=
"paragraph"><p>Multiple --notes options can be combined to control which notes are
897 being displayed. Examples:
"--notes=foo" will show only notes from
898 "refs/notes/foo";
"--notes=foo --notes" will show both notes from
899 "refs/notes/foo" and from the default notes ref(s).
</p></div>
906 Do not show notes. This negates the above
<code>--notes
</code> option, by
907 resetting the list of notes refs from which notes are shown.
908 Options are parsed in the order given on the command line, so e.g.
909 "--notes --notes=foo --no-notes --notes=bar" will only show notes
910 from
"refs/notes/bar".
914 --show-notes[=
<ref
>]
917 --[no-]standard-notes
921 These options are deprecated. Use the above --notes/--no-notes
930 Check the validity of a signed commit object by passing the signature
931 to
<code>gpg --verify
</code> and show the output.
938 <h2 id=
"_pretty_formats">PRETTY FORMATS
</h2>
939 <div class=
"sectionbody">
940 <div class=
"paragraph"><p>If the commit is a merge, and if the pretty-format
941 is not
<em>oneline
</em>,
<em>email
</em> or
<em>raw
</em>, an additional line is
942 inserted before the
<em>Author:
</em> line. This line begins with
943 "Merge: " and the hashes of ancestral commits are printed,
944 separated by spaces. Note that the listed commits may not
945 necessarily be the list of the
<strong>direct
</strong> parent commits if you
946 have limited your view of history: for example, if you are
947 only interested in changes related to a certain directory or
949 <div class=
"paragraph"><p>There are several built-in formats, and you can define
950 additional formats by setting a pretty.
<name
>
951 config option to either another format name, or a
952 <em>format:
</em> string, as described below (see
953 <a href=
"git-config.html">git-config(
1)
</a>). Here are the details of the
954 built-in formats:
</p></div>
955 <div class=
"ulist"><ul>
960 <div class=
"literalblock">
961 <div class=
"content">
962 <pre><code><hash
> <title-line
></code></pre>
964 <div class=
"paragraph"><p>This is designed to be as compact as possible.
</p></div>
970 <div class=
"literalblock">
971 <div class=
"content">
972 <pre><code>commit
<hash
>
973 Author:
<author
></code></pre>
975 <div class=
"literalblock">
976 <div class=
"content">
977 <pre><code><title-line
></code></pre>
984 <div class=
"literalblock">
985 <div class=
"content">
986 <pre><code>commit
<hash
>
987 Author:
<author
>
988 Date:
<author-date
></code></pre>
990 <div class=
"literalblock">
991 <div class=
"content">
992 <pre><code><title-line
></code></pre>
994 <div class=
"literalblock">
995 <div class=
"content">
996 <pre><code><full-commit-message
></code></pre>
1003 <div class=
"literalblock">
1004 <div class=
"content">
1005 <pre><code>commit
<hash
>
1006 Author:
<author
>
1007 Commit:
<committer
></code></pre>
1009 <div class=
"literalblock">
1010 <div class=
"content">
1011 <pre><code><title-line
></code></pre>
1013 <div class=
"literalblock">
1014 <div class=
"content">
1015 <pre><code><full-commit-message
></code></pre>
1022 <div class=
"literalblock">
1023 <div class=
"content">
1024 <pre><code>commit
<hash
>
1025 Author:
<author
>
1026 AuthorDate:
<author-date
>
1027 Commit:
<committer
>
1028 CommitDate:
<committer-date
></code></pre>
1030 <div class=
"literalblock">
1031 <div class=
"content">
1032 <pre><code><title-line
></code></pre>
1034 <div class=
"literalblock">
1035 <div class=
"content">
1036 <pre><code><full-commit-message
></code></pre>
1043 <div class=
"literalblock">
1044 <div class=
"content">
1045 <pre><code><abbrev-hash
> (
<title-line
>,
<short-author-date
>)
</code></pre>
1047 <div class=
"paragraph"><p>This format is used to refer to another commit in a commit message and
1048 is the same as
<code>--pretty='format:%C(auto)%h (%s, %ad)'
</code>. By default,
1049 the date is formatted with
<code>--date=short
</code> unless another
<code>--date
</code> option
1050 is explicitly specified. As with any
<code>format:
</code> with format
1051 placeholders, its output is not affected by other options like
1052 <code>--decorate
</code> and
<code>--walk-reflogs
</code>.
</p></div>
1058 <div class=
"literalblock">
1059 <div class=
"content">
1060 <pre><code>From
<hash
> <date
>
1061 From:
<author
>
1062 Date:
<author-date
>
1063 Subject: [PATCH]
<title-line
></code></pre>
1065 <div class=
"literalblock">
1066 <div class=
"content">
1067 <pre><code><full-commit-message
></code></pre>
1074 <div class=
"paragraph"><p>Like
<em>email
</em>, but lines in the commit message starting with
"From "
1075 (preceded by zero or more
">") are quoted with
">" so they aren
’t
1076 confused as starting a new commit.
</p></div>
1082 <div class=
"paragraph"><p>The
<em>raw
</em> format shows the entire commit exactly as
1083 stored in the commit object. Notably, the hashes are
1084 displayed in full, regardless of whether --abbrev or
1085 --no-abbrev are used, and
<em>parents
</em> information show the
1086 true parent commits, without taking grafts or history
1087 simplification into account. Note that this format affects the way
1088 commits are displayed, but not the way the diff is shown e.g. with
1089 <code>git log --raw
</code>. To get full object names in a raw diff format,
1090 use
<code>--no-abbrev
</code>.
</p></div>
1094 <em>format:
<format-string
></em>
1096 <div class=
"paragraph"><p>The
<em>format:
<format-string
></em> format allows you to specify which information
1097 you want to show. It works a little bit like printf format,
1098 with the notable exception that you get a newline with
<em>%n
</em>
1099 instead of
<em>\n
</em>.
</p></div>
1100 <div class=
"paragraph"><p>E.g,
<em>format:
"The author of %h was %an, %ar%nThe title was >>%s<<%n"</em>
1101 would show something like this:
</p></div>
1102 <div class=
"listingblock">
1103 <div class=
"content">
1104 <pre><code>The author of fe6e0ee was Junio C Hamano,
23 hours ago
1105 The title was
>>t4119: test autocomputing -p
<n
> for traditional diff input.
<<</code></pre>
1107 <div class=
"paragraph"><p>The placeholders are:
</p></div>
1108 <div class=
"ulist"><ul>
1111 Placeholders that expand to a single literal character:
1113 <div class=
"dlist"><dl>
1114 <dt class=
"hdlist1">
1122 <dt class=
"hdlist1">
1130 <dt class=
"hdlist1">
1135 print a byte from a hex code
1142 Placeholders that affect formatting of later placeholders:
1144 <div class=
"dlist"><dl>
1145 <dt class=
"hdlist1">
1153 <dt class=
"hdlist1">
1158 switch color to green
1161 <dt class=
"hdlist1">
1166 switch color to blue
1169 <dt class=
"hdlist1">
1177 <dt class=
"hdlist1">
1178 <em>%C(
…)
</em>
1182 color specification, as described under Values in the
1183 "CONFIGURATION FILE" section of
<a href=
"git-config.html">git-config(
1)
</a>. By
1184 default, colors are shown only when enabled for log output
1185 (by
<code>color.diff
</code>,
<code>color.ui
</code>, or
<code>--color
</code>, and respecting
1186 the
<code>auto
</code> settings of the former if we are going to a
1187 terminal).
<code>%C(auto,...)
</code> is accepted as a historical
1188 synonym for the default (e.g.,
<code>%C(auto,red)
</code>). Specifying
1189 <code>%C(always,...)
</code> will show the colors even when color is
1190 not otherwise enabled (though consider just using
1191 <code>--color=always
</code> to enable color for the whole output,
1192 including this format and anything else git might color).
1193 <code>auto
</code> alone (i.e.
<code>%C(auto)
</code>) will turn on auto coloring
1194 on the next placeholders until the color is switched
1198 <dt class=
"hdlist1">
1203 left (
<code><</code>), right (
<code>></code>) or boundary (
<code>-
</code>) mark
1206 <dt class=
"hdlist1">
1207 <em>%w([
<w
>[,
<i1
>[,
<i2
>]]])
</em>
1211 switch line wrapping, like the -w option of
1212 <a href=
"git-shortlog.html">git-shortlog(
1)
</a>.
1215 <dt class=
"hdlist1">
1216 <em>%
<(
<N
> [,trunc|ltrunc|mtrunc])
</em>
1220 make the next placeholder take at
1221 least N column widths, padding spaces on
1222 the right if necessary. Optionally
1223 truncate (with ellipsis
<em>..
</em>) at the left (ltrunc)
<code>..ft
</code>,
1224 the middle (mtrunc)
<code>mi..le
</code>, or the end
1225 (trunc)
<code>rig..
</code>, if the output is longer than
1227 Note
1: that truncating
1228 only works correctly with N
>=
2.
1229 Note
2: spaces around the N and M (see below)
1230 values are optional.
1231 Note
3: Emojis and other wide characters
1232 will take two display columns, which may
1233 over-run column boundaries.
1234 Note
4: decomposed character combining marks
1235 may be misplaced at padding boundaries.
1238 <dt class=
"hdlist1">
1239 <em>%
<|(
<M
> )
</em>
1243 make the next placeholder take at least until Mth
1244 display column, padding spaces on the right if necessary.
1245 Use negative M values for column positions measured
1246 from the right hand edge of the terminal window.
1249 <dt class=
"hdlist1">
1250 <em>%
>(
<N
> )
</em>,
<em>%
>|(
<M
> )
</em>
1254 similar to
<em>%
<(
<N
> )
</em>,
<em>%
<|(
<M
> )
</em> respectively,
1255 but padding spaces on the left
1258 <dt class=
"hdlist1">
1259 <em>%
>>(
<N
> )
</em>,
<em>%
>>|(
<M
> )
</em>
1263 similar to
<em>%
>(
<N
> )
</em>,
<em>%
>|(
<M
> )
</em>
1264 respectively, except that if the next
1265 placeholder takes more spaces than given and
1266 there are spaces on its left, use those
1270 <dt class=
"hdlist1">
1271 <em>%
><(
<N
> )
</em>,
<em>%
><|(
<M
> )
</em>
1275 similar to
<em>%
<(
<N
> )
</em>,
<em>%
<|(
<M
> )
</em>
1276 respectively, but padding both sides
1277 (i.e. the text is centered)
1284 Placeholders that expand to information extracted from the commit:
1286 <div class=
"dlist"><dl>
1287 <dt class=
"hdlist1">
1295 <dt class=
"hdlist1">
1300 abbreviated commit hash
1303 <dt class=
"hdlist1">
1311 <dt class=
"hdlist1">
1316 abbreviated tree hash
1319 <dt class=
"hdlist1">
1327 <dt class=
"hdlist1">
1332 abbreviated parent hashes
1335 <dt class=
"hdlist1">
1343 <dt class=
"hdlist1">
1348 author name (respecting .mailmap, see
<a href=
"git-shortlog.html">git-shortlog(
1)
</a>
1349 or
<a href=
"git-blame.html">git-blame(
1)
</a>)
1352 <dt class=
"hdlist1">
1360 <dt class=
"hdlist1">
1365 author email (respecting .mailmap, see
<a href=
"git-shortlog.html">git-shortlog(
1)
</a>
1366 or
<a href=
"git-blame.html">git-blame(
1)
</a>)
1369 <dt class=
"hdlist1">
1374 author email local-part (the part before the
<em>@
</em> sign)
1377 <dt class=
"hdlist1">
1382 author local-part (see
<em>%al
</em>) respecting .mailmap, see
1383 <a href=
"git-shortlog.html">git-shortlog(
1)
</a> or
<a href=
"git-blame.html">git-blame(
1)
</a>)
1386 <dt class=
"hdlist1">
1391 author date (format respects --date= option)
1394 <dt class=
"hdlist1">
1399 author date, RFC2822 style
1402 <dt class=
"hdlist1">
1407 author date, relative
1410 <dt class=
"hdlist1">
1415 author date, UNIX timestamp
1418 <dt class=
"hdlist1">
1423 author date, ISO
8601-like format
1426 <dt class=
"hdlist1">
1431 author date, strict ISO
8601 format
1434 <dt class=
"hdlist1">
1439 author date, short format (
<code>YYYY-MM-DD
</code>)
1442 <dt class=
"hdlist1">
1447 author date, human style (like the
<code>--date=human
</code> option of
1448 <a href=
"git-rev-list.html">git-rev-list(
1)
</a>)
1451 <dt class=
"hdlist1">
1459 <dt class=
"hdlist1">
1464 committer name (respecting .mailmap, see
1465 <a href=
"git-shortlog.html">git-shortlog(
1)
</a> or
<a href=
"git-blame.html">git-blame(
1)
</a>)
1468 <dt class=
"hdlist1">
1476 <dt class=
"hdlist1">
1481 committer email (respecting .mailmap, see
1482 <a href=
"git-shortlog.html">git-shortlog(
1)
</a> or
<a href=
"git-blame.html">git-blame(
1)
</a>)
1485 <dt class=
"hdlist1">
1490 committer email local-part (the part before the
<em>@
</em> sign)
1493 <dt class=
"hdlist1">
1498 committer local-part (see
<em>%cl
</em>) respecting .mailmap, see
1499 <a href=
"git-shortlog.html">git-shortlog(
1)
</a> or
<a href=
"git-blame.html">git-blame(
1)
</a>)
1502 <dt class=
"hdlist1">
1507 committer date (format respects --date= option)
1510 <dt class=
"hdlist1">
1515 committer date, RFC2822 style
1518 <dt class=
"hdlist1">
1523 committer date, relative
1526 <dt class=
"hdlist1">
1531 committer date, UNIX timestamp
1534 <dt class=
"hdlist1">
1539 committer date, ISO
8601-like format
1542 <dt class=
"hdlist1">
1547 committer date, strict ISO
8601 format
1550 <dt class=
"hdlist1">
1555 committer date, short format (
<code>YYYY-MM-DD
</code>)
1558 <dt class=
"hdlist1">
1563 committer date, human style (like the
<code>--date=human
</code> option of
1564 <a href=
"git-rev-list.html">git-rev-list(
1)
</a>)
1567 <dt class=
"hdlist1">
1572 ref names, like the --decorate option of
<a href=
"git-log.html">git-log(
1)
</a>
1575 <dt class=
"hdlist1">
1580 ref names without the
" (",
")" wrapping.
1583 <dt class=
"hdlist1">
1584 <em>%(describe[:options])
</em>
1588 human-readable name, like
1589 <a href=
"git-describe.html">git-describe(
1)
</a>; empty string for
1590 undescribable commits. The
<code>describe
</code> string
1591 may be followed by a colon and zero or more
1592 comma-separated options. Descriptions can be
1593 inconsistent when tags are added or removed at
1596 <div class=
"ulist"><ul>
1599 <em>tags[=
<bool-value
>]
</em>: Instead of only considering annotated tags,
1600 consider lightweight tags as well.
1605 <em>abbrev=
<number
></em>: Instead of using the default number of hexadecimal digits
1606 (which will vary according to the number of objects in the repository with a
1607 default of
7) of the abbreviated object name, use
<number
> digits, or as many
1608 digits as needed to form a unique object name.
1613 <em>match=
<pattern
></em>: Only consider tags matching the given
1614 <code>glob(
7)
</code> pattern, excluding the
"refs/tags/" prefix.
1619 <em>exclude=
<pattern
></em>: Do not consider tags matching the given
1620 <code>glob(
7)
</code> pattern, excluding the
"refs/tags/" prefix.
1625 <dt class=
"hdlist1">
1630 ref name given on the command line by which the commit was reached
1631 (like
<code>git log --source
</code>), only works with
<code>git log
</code>
1634 <dt class=
"hdlist1">
1642 <dt class=
"hdlist1">
1650 <dt class=
"hdlist1">
1655 sanitized subject line, suitable for a filename
1658 <dt class=
"hdlist1">
1666 <dt class=
"hdlist1">
1671 raw body (unwrapped subject and body)
1674 <dt class=
"hdlist1">
1682 <dt class=
"hdlist1">
1687 raw verification message from GPG for a signed commit
1690 <dt class=
"hdlist1">
1695 show
"G" for a good (valid) signature,
1696 "B" for a bad signature,
1697 "U" for a good signature with unknown validity,
1698 "X" for a good signature that has expired,
1699 "Y" for a good signature made by an expired key,
1700 "R" for a good signature made by a revoked key,
1701 "E" if the signature cannot be checked (e.g. missing key)
1702 and
"N" for no signature
1705 <dt class=
"hdlist1">
1710 show the name of the signer for a signed commit
1713 <dt class=
"hdlist1">
1718 show the key used to sign a signed commit
1721 <dt class=
"hdlist1">
1726 show the fingerprint of the key used to sign a signed commit
1729 <dt class=
"hdlist1">
1734 show the fingerprint of the primary key whose subkey was used
1735 to sign a signed commit
1738 <dt class=
"hdlist1">
1743 show the trust level for the key used to sign a signed commit
1746 <dt class=
"hdlist1">
1751 reflog selector, e.g.,
<code>refs/stash@{
1}
</code> or
<code>refs/stash@{
2
1752 minutes ago}
</code>; the format follows the rules described for the
1753 <code>-g
</code> option. The portion before the
<code>@
</code> is the refname as
1754 given on the command line (so
<code>git log -g refs/heads/master
</code>
1755 would yield
<code>refs/heads/master@{
0}
</code>).
1758 <dt class=
"hdlist1">
1763 shortened reflog selector; same as
<code>%gD
</code>, but the refname
1764 portion is shortened for human readability (so
1765 <code>refs/heads/master
</code> becomes just
<code>master
</code>).
1768 <dt class=
"hdlist1">
1773 reflog identity name
1776 <dt class=
"hdlist1">
1781 reflog identity name (respecting .mailmap, see
1782 <a href=
"git-shortlog.html">git-shortlog(
1)
</a> or
<a href=
"git-blame.html">git-blame(
1)
</a>)
1785 <dt class=
"hdlist1">
1790 reflog identity email
1793 <dt class=
"hdlist1">
1798 reflog identity email (respecting .mailmap, see
1799 <a href=
"git-shortlog.html">git-shortlog(
1)
</a> or
<a href=
"git-blame.html">git-blame(
1)
</a>)
1802 <dt class=
"hdlist1">
1810 <dt class=
"hdlist1">
1811 <em>%(trailers[:options])
</em>
1815 display the trailers of the body as
1817 <a href=
"git-interpret-trailers.html">git-interpret-trailers(
1)
</a>. The
1818 <code>trailers
</code> string may be followed by a colon
1819 and zero or more comma-separated options.
1820 If any option is provided multiple times the
1821 last occurrence wins.
1823 <div class=
"ulist"><ul>
1826 <em>key=
<key
></em>: only show trailers with specified
<key
>. Matching is done
1827 case-insensitively and trailing colon is optional. If option is
1828 given multiple times trailer lines matching any of the keys are
1829 shown. This option automatically enables the
<code>only
</code> option so that
1830 non-trailer lines in the trailer block are hidden. If that is not
1831 desired it can be disabled with
<code>only=false
</code>. E.g.,
1832 <code>%(trailers:key=Reviewed-by)
</code> shows trailer lines with key
1833 <code>Reviewed-by
</code>.
1838 <em>only[=
<bool
>]
</em>: select whether non-trailer lines from the trailer
1839 block should be included.
1844 <em>separator=
<sep
></em>: specify a separator inserted between trailer
1845 lines. When this option is not given each trailer line is
1846 terminated with a line feed character. The string
<sep
> may contain
1847 the literal formatting codes described above. To use comma as
1848 separator one must use
<code>%x2C
</code> as it would otherwise be parsed as
1849 next option. E.g.,
<code>%(trailers:key=Ticket,separator=%x2C )
</code>
1850 shows all trailer lines whose key is
"Ticket" separated by a comma
1856 <em>unfold[=
<bool
>]
</em>: make it behave as if interpret-trailer
’s
<code>--unfold
</code>
1857 option was given. E.g.,
1858 <code>%(trailers:only,unfold=true)
</code> unfolds and shows all trailer lines.
1863 <em>keyonly[=
<bool
>]
</em>: only show the key part of the trailer.
1868 <em>valueonly[=
<bool
>]
</em>: only show the value part of the trailer.
1873 <em>key_value_separator=
<sep
></em>: specify a separator inserted between
1874 trailer lines. When this option is not given each trailer key-value
1875 pair is separated by
": ". Otherwise it shares the same semantics
1876 as
<em>separator=
<sep
></em> above.
1886 <div class=
"admonitionblock">
1889 <div class=
"title">Note
</div>
1891 <td class=
"content">Some placeholders may depend on other options given to the
1892 revision traversal engine. For example, the
<code>%g*
</code> reflog options will
1893 insert an empty string unless we are traversing reflog entries (e.g., by
1894 <code>git log -g
</code>). The
<code>%d
</code> and
<code>%D
</code> placeholders will use the
"short"
1895 decoration format if
<code>--decorate
</code> was not already provided on the command
1899 <div class=
"paragraph"><p>The boolean options accept an optional value
<code>[=
<bool-value
>]
</code>. The values
1900 <code>true
</code>,
<code>false
</code>,
<code>on
</code>,
<code>off
</code> etc. are all accepted. See the
"boolean"
1901 sub-section in
"EXAMPLES" in
<a href=
"git-config.html">git-config(
1)
</a>. If a boolean
1902 option is given with no value, it
’s enabled.
</p></div>
1903 <div class=
"paragraph"><p>If you add a
<code>+
</code> (plus sign) after
<em>%
</em> of a placeholder, a line-feed
1904 is inserted immediately before the expansion if and only if the
1905 placeholder expands to a non-empty string.
</p></div>
1906 <div class=
"paragraph"><p>If you add a
<code>-
</code> (minus sign) after
<em>%
</em> of a placeholder, all consecutive
1907 line-feeds immediately preceding the expansion are deleted if and only if the
1908 placeholder expands to an empty string.
</p></div>
1909 <div class=
"paragraph"><p>If you add a ` ` (space) after
<em>%
</em> of a placeholder, a space
1910 is inserted immediately before the expansion if and only if the
1911 placeholder expands to a non-empty string.
</p></div>
1912 <div class=
"ulist"><ul>
1917 <div class=
"paragraph"><p>The
<em>tformat:
</em> format works exactly like
<em>format:
</em>, except that it
1918 provides
"terminator" semantics instead of
"separator" semantics. In
1919 other words, each commit has the message terminator character (usually a
1920 newline) appended, rather than a separator placed between entries.
1921 This means that the final entry of a single-line format will be properly
1922 terminated with a new line, just as the
"oneline" format does.
1923 For example:
</p></div>
1924 <div class=
"listingblock">
1925 <div class=
"content">
1926 <pre><code>$ git log -
2 --pretty=format:%h
4da45bef \
1927 | perl -pe '$_ .=
" -- NO NEWLINE\n" unless /\n/'
1929 7134973 -- NO NEWLINE
1931 $ git log -
2 --pretty=tformat:%h
4da45bef \
1932 | perl -pe '$_ .=
" -- NO NEWLINE\n" unless /\n/'
1934 7134973</code></pre>
1936 <div class=
"paragraph"><p>In addition, any unrecognized string that has a
<code>%
</code> in it is interpreted
1937 as if it has
<code>tformat:
</code> in front of it. For example, these two are
1938 equivalent:
</p></div>
1939 <div class=
"listingblock">
1940 <div class=
"content">
1941 <pre><code>$ git log -
2 --pretty=tformat:%h
4da45bef
1942 $ git log -
2 --pretty=%h
4da45bef
</code></pre>
1949 <h2 id=
"_diff_formatting">DIFF FORMATTING
</h2>
1950 <div class=
"sectionbody">
1951 <div class=
"paragraph"><p>The options below can be used to change the way
<code>git show
</code> generates
1952 diff output.
</p></div>
1953 <div class=
"dlist"><dl>
1954 <dt class=
"hdlist1">
1957 <dt class=
"hdlist1">
1960 <dt class=
"hdlist1">
1965 Generate patch (see section titled
1966 <a href=
"#generate_patch_text_with_p">"Generating patch text with -p"</a>).
1969 <dt class=
"hdlist1">
1972 <dt class=
"hdlist1">
1977 Suppress all output from the diff machinery. Useful for
1978 commands like
<code>git show
</code> that show the patch by default to
1979 squelch their output, or to cancel the effect of options like
1980 <code>--patch
</code>,
<code>--stat
</code> earlier on the command line in an alias.
1983 <dt class=
"hdlist1">
1984 --diff-merges=(off|none|on|first-parent|
1|separate|m|combined|c|dense-combined|cc|remerge|r)
1986 <dt class=
"hdlist1">
1991 Specify diff format to be used for merge commits. Default is
1992 <code>dense-combined
</code> unless
<code>--first-parent
</code> is in use, in which case
1993 <code>first-parent
</code> is the default.
1995 <div class=
"dlist"><dl>
1996 <dt class=
"hdlist1">
1997 --diff-merges=(off|none)
1999 <dt class=
"hdlist1">
2004 Disable output of diffs for merge commits. Useful to override
2008 <dt class=
"hdlist1">
2011 <dt class=
"hdlist1">
2014 <dt class=
"hdlist1">
2019 This option makes diff output for merge commits to be shown in
2020 the default format.
<code>-m
</code> will produce the output only if
<code>-p
</code>
2021 is given as well. The default format could be changed using
2022 <code>log.diffMerges
</code> configuration parameter, which default value
2023 is
<code>separate
</code>.
2026 <dt class=
"hdlist1">
2027 --diff-merges=first-parent
2029 <dt class=
"hdlist1">
2034 This option makes merge commits show the full diff with
2035 respect to the first parent only.
2038 <dt class=
"hdlist1">
2039 --diff-merges=separate
2043 This makes merge commits show the full diff with respect to
2044 each of the parents. Separate log entry and diff is generated
2048 <dt class=
"hdlist1">
2049 --diff-merges=remerge
2051 <dt class=
"hdlist1">
2054 <dt class=
"hdlist1">
2059 With this option, two-parent merge commits are remerged to
2060 create a temporary tree object
 — potentially containing files
2061 with conflict markers and such. A diff is then shown between
2062 that temporary tree and the actual merge commit.
2064 <div class=
"paragraph"><p>The output emitted when this option is used is subject to change, and
2065 so is its interaction with other options (unless explicitly
2066 documented).
</p></div>
2068 <dt class=
"hdlist1">
2069 --diff-merges=combined
2071 <dt class=
"hdlist1">
2074 <dt class=
"hdlist1">
2079 With this option, diff output for a merge commit shows the
2080 differences from each of the parents to the merge result
2081 simultaneously instead of showing pairwise diff between a
2082 parent and the result one at a time. Furthermore, it lists
2083 only files which were modified from all parents.
<code>-c
</code> implies
2087 <dt class=
"hdlist1">
2088 --diff-merges=dense-combined
2090 <dt class=
"hdlist1">
2093 <dt class=
"hdlist1">
2098 With this option the output produced by
2099 <code>--diff-merges=combined
</code> is further compressed by omitting
2100 uninteresting hunks whose contents in the parents have only
2101 two variants and the merge result picks one of them without
2102 modification.
<code>--cc
</code> implies
<code>-p
</code>.
2107 <dt class=
"hdlist1">
2108 --combined-all-paths
2112 This flag causes combined diffs (used for merge commits) to
2113 list the name of the file from all parents. It thus only has
2114 effect when
<code>--diff-merges=[dense-]combined
</code> is in use, and
2115 is likely only useful if filename changes are detected (i.e.
2116 when either rename or copy detection have been requested).
2119 <dt class=
"hdlist1">
2122 <dt class=
"hdlist1">
2127 Generate diffs with
<n
> lines of context instead of
2129 Implies
<code>--patch
</code>.
2132 <dt class=
"hdlist1">
2133 --output=
<file
>
2137 Output to a specific file instead of stdout.
2140 <dt class=
"hdlist1">
2141 --output-indicator-new=
<char
>
2143 <dt class=
"hdlist1">
2144 --output-indicator-old=
<char
>
2146 <dt class=
"hdlist1">
2147 --output-indicator-context=
<char
>
2151 Specify the character used to indicate new, old or context
2152 lines in the generated patch. Normally they are
<em>+
</em>,
<em>-
</em> and
2156 <dt class=
"hdlist1">
2161 For each commit, show a summary of changes using the raw diff
2162 format. See the
"RAW OUTPUT FORMAT" section of
2163 <a href=
"git-diff.html">git-diff(
1)
</a>. This is different from showing the log
2164 itself in raw format, which you can achieve with
2165 <code>--format=raw
</code>.
2168 <dt class=
"hdlist1">
2173 Synonym for
<code>-p --raw
</code>.
2176 <dt class=
"hdlist1">
2181 Show the tree objects in the diff output.
2184 <dt class=
"hdlist1">
2189 Enable the heuristic that shifts diff hunk boundaries to make patches
2190 easier to read. This is the default.
2193 <dt class=
"hdlist1">
2194 --no-indent-heuristic
2198 Disable the indent heuristic.
2201 <dt class=
"hdlist1">
2206 Spend extra time to make sure the smallest possible
2210 <dt class=
"hdlist1">
2215 Generate a diff using the
"patience diff" algorithm.
2218 <dt class=
"hdlist1">
2223 Generate a diff using the
"histogram diff" algorithm.
2226 <dt class=
"hdlist1">
2227 --anchored=
<text
>
2231 Generate a diff using the
"anchored diff" algorithm.
2233 <div class=
"paragraph"><p>This option may be specified more than once.
</p></div>
2234 <div class=
"paragraph"><p>If a line exists in both the source and destination, exists only once,
2235 and starts with this text, this algorithm attempts to prevent it from
2236 appearing as a deletion or addition in the output. It uses the
"patience
2237 diff" algorithm internally.
</p></div>
2239 <dt class=
"hdlist1">
2240 --diff-algorithm={patience|minimal|histogram|myers}
2244 Choose a diff algorithm. The variants are as follows:
2246 <div class=
"openblock">
2247 <div class=
"content">
2248 <div class=
"dlist"><dl>
2249 <dt class=
"hdlist1">
2250 <code>default
</code>,
<code>myers
</code>
2254 The basic greedy diff algorithm. Currently, this is the default.
2257 <dt class=
"hdlist1">
2258 <code>minimal
</code>
2262 Spend extra time to make sure the smallest possible diff is
2266 <dt class=
"hdlist1">
2267 <code>patience
</code>
2271 Use
"patience diff" algorithm when generating patches.
2274 <dt class=
"hdlist1">
2275 <code>histogram
</code>
2279 This algorithm extends the patience algorithm to
"support
2280 low-occurrence common elements".
2285 <div class=
"paragraph"><p>For instance, if you configured the
<code>diff.algorithm
</code> variable to a
2286 non-default value and want to use the default one, then you
2287 have to use
<code>--diff-algorithm=default
</code> option.
</p></div>
2289 <dt class=
"hdlist1">
2290 --stat[=
<width
>[,
<name-width
>[,
<count
>]]]
2294 Generate a diffstat. By default, as much space as necessary
2295 will be used for the filename part, and the rest for the graph
2296 part. Maximum width defaults to terminal width, or
80 columns
2297 if not connected to a terminal, and can be overridden by
2298 <code><width
></code>. The width of the filename part can be limited by
2299 giving another width
<code><name-width
></code> after a comma. The width
2300 of the graph part can be limited by using
2301 <code>--stat-graph-width=
<width
></code> (affects all commands generating
2302 a stat graph) or by setting
<code>diff.statGraphWidth=
<width
></code>
2303 (does not affect
<code>git format-patch
</code>).
2304 By giving a third parameter
<code><count
></code>, you can limit the
2305 output to the first
<code><count
></code> lines, followed by
<code>...
</code> if
2308 <div class=
"paragraph"><p>These parameters can also be set individually with
<code>--stat-width=
<width
></code>,
2309 <code>--stat-name-width=
<name-width
></code> and
<code>--stat-count=
<count
></code>.
</p></div>
2311 <dt class=
"hdlist1">
2316 Output a condensed summary of extended header information such
2317 as file creations or deletions (
"new" or
"gone", optionally
"+l"
2318 if it
’s a symlink) and mode changes (
"+x" or
"-x" for adding
2319 or removing executable bit respectively) in diffstat. The
2320 information is put between the filename part and the graph
2321 part. Implies
<code>--stat
</code>.
2324 <dt class=
"hdlist1">
2329 Similar to
<code>--stat
</code>, but shows number of added and
2330 deleted lines in decimal notation and pathname without
2331 abbreviation, to make it more machine friendly. For
2332 binary files, outputs two
<code>-
</code> instead of saying
2336 <dt class=
"hdlist1">
2341 Output only the last line of the
<code>--stat
</code> format containing total
2342 number of modified files, as well as number of added and deleted
2346 <dt class=
"hdlist1">
2347 -X[
<param1,param2,
…>]
2349 <dt class=
"hdlist1">
2350 --dirstat[=
<param1,param2,
…>]
2354 Output the distribution of relative amount of changes for each
2355 sub-directory. The behavior of
<code>--dirstat
</code> can be customized by
2356 passing it a comma separated list of parameters.
2357 The defaults are controlled by the
<code>diff.dirstat
</code> configuration
2358 variable (see
<a href=
"git-config.html">git-config(
1)
</a>).
2359 The following parameters are available:
2361 <div class=
"openblock">
2362 <div class=
"content">
2363 <div class=
"dlist"><dl>
2364 <dt class=
"hdlist1">
2365 <code>changes
</code>
2369 Compute the dirstat numbers by counting the lines that have been
2370 removed from the source, or added to the destination. This ignores
2371 the amount of pure code movements within a file. In other words,
2372 rearranging lines in a file is not counted as much as other changes.
2373 This is the default behavior when no parameter is given.
2376 <dt class=
"hdlist1">
2381 Compute the dirstat numbers by doing the regular line-based diff
2382 analysis, and summing the removed/added line counts. (For binary
2383 files, count
64-byte chunks instead, since binary files have no
2384 natural concept of lines). This is a more expensive
<code>--dirstat
</code>
2385 behavior than the
<code>changes
</code> behavior, but it does count rearranged
2386 lines within a file as much as other changes. The resulting output
2387 is consistent with what you get from the other
<code>--*stat
</code> options.
2390 <dt class=
"hdlist1">
2395 Compute the dirstat numbers by counting the number of files changed.
2396 Each changed file counts equally in the dirstat analysis. This is
2397 the computationally cheapest
<code>--dirstat
</code> behavior, since it does
2398 not have to look at the file contents at all.
2401 <dt class=
"hdlist1">
2402 <code>cumulative
</code>
2406 Count changes in a child directory for the parent directory as well.
2407 Note that when using
<code>cumulative
</code>, the sum of the percentages
2408 reported may exceed
100%. The default (non-cumulative) behavior can
2409 be specified with the
<code>noncumulative
</code> parameter.
2412 <dt class=
"hdlist1">
2417 An integer parameter specifies a cut-off percent (
3% by default).
2418 Directories contributing less than this percentage of the changes
2419 are not shown in the output.
2424 <div class=
"paragraph"><p>Example: The following will count changed files, while ignoring
2425 directories with less than
10% of the total amount of changed files,
2426 and accumulating child directory counts in the parent directories:
2427 <code>--dirstat=files,
10,cumulative
</code>.
</p></div>
2429 <dt class=
"hdlist1">
2434 Synonym for --dirstat=cumulative
2437 <dt class=
"hdlist1">
2438 --dirstat-by-file[=
<param1,param2
>…]
2442 Synonym for --dirstat=files,param1,param2
…
2445 <dt class=
"hdlist1">
2450 Output a condensed summary of extended header information
2451 such as creations, renames and mode changes.
2454 <dt class=
"hdlist1">
2459 Synonym for
<code>-p --stat
</code>.
2462 <dt class=
"hdlist1">
2467 Separate the commits with NULs instead of with new newlines.
2469 <div class=
"paragraph"><p>Also, when
<code>--raw
</code> or
<code>--numstat
</code> has been given, do not munge
2470 pathnames and use NULs as output field terminators.
</p></div>
2471 <div class=
"paragraph"><p>Without this option, pathnames with
"unusual" characters are quoted as
2472 explained for the configuration variable
<code>core.quotePath
</code> (see
2473 <a href=
"git-config.html">git-config(
1)
</a>).
</p></div>
2475 <dt class=
"hdlist1">
2480 Show only names of changed files. The file names are often encoded in UTF-
8.
2481 For more information see the discussion about encoding in the
<a href=
"git-log.html">git-log(
1)
</a>
2485 <dt class=
"hdlist1">
2490 Show only names and status of changed files. See the description
2491 of the
<code>--diff-filter
</code> option on what the status letters mean.
2492 Just like
<code>--name-only
</code> the file names are often encoded in UTF-
8.
2495 <dt class=
"hdlist1">
2496 --submodule[=
<format
>]
2500 Specify how differences in submodules are shown. When specifying
2501 <code>--submodule=short
</code> the
<em>short
</em> format is used. This format just
2502 shows the names of the commits at the beginning and end of the range.
2503 When
<code>--submodule
</code> or
<code>--submodule=log
</code> is specified, the
<em>log
</em>
2504 format is used. This format lists the commits in the range like
2505 <a href=
"git-submodule.html">git-submodule(
1)
</a> <code>summary
</code> does. When
<code>--submodule=diff
</code>
2506 is specified, the
<em>diff
</em> format is used. This format shows an
2507 inline diff of the changes in the submodule contents between the
2508 commit range. Defaults to
<code>diff.submodule
</code> or the
<em>short
</em> format
2509 if the config option is unset.
2512 <dt class=
"hdlist1">
2513 --color[=
<when
>]
2518 <code>--color
</code> (i.e. without
<em>=
<when
></em>) is the same as
<code>--color=always
</code>.
2519 <em><when
></em> can be one of
<code>always
</code>,
<code>never
</code>, or
<code>auto
</code>.
2522 <dt class=
"hdlist1">
2527 Turn off colored diff.
2528 It is the same as
<code>--color=never
</code>.
2531 <dt class=
"hdlist1">
2532 --color-moved[=
<mode
>]
2536 Moved lines of code are colored differently.
2537 The
<mode
> defaults to
<em>no
</em> if the option is not given
2538 and to
<em>zebra
</em> if the option with no mode is given.
2539 The mode must be one of:
2541 <div class=
"openblock">
2542 <div class=
"content">
2543 <div class=
"dlist"><dl>
2544 <dt class=
"hdlist1">
2549 Moved lines are not highlighted.
2552 <dt class=
"hdlist1">
2557 Is a synonym for
<code>zebra
</code>. This may change to a more sensible mode
2561 <dt class=
"hdlist1">
2566 Any line that is added in one location and was removed
2567 in another location will be colored with
<em>color.diff.newMoved
</em>.
2568 Similarly
<em>color.diff.oldMoved
</em> will be used for removed lines
2569 that are added somewhere else in the diff. This mode picks up any
2570 moved line, but it is not very useful in a review to determine
2571 if a block of code was moved without permutation.
2574 <dt class=
"hdlist1">
2579 Blocks of moved text of at least
20 alphanumeric characters
2580 are detected greedily. The detected blocks are
2581 painted using either the
<em>color.diff.{old,new}Moved
</em> color.
2582 Adjacent blocks cannot be told apart.
2585 <dt class=
"hdlist1">
2590 Blocks of moved text are detected as in
<em>blocks
</em> mode. The blocks
2591 are painted using either the
<em>color.diff.{old,new}Moved
</em> color or
2592 <em>color.diff.{old,new}MovedAlternative
</em>. The change between
2593 the two colors indicates that a new block was detected.
2596 <dt class=
"hdlist1">
2601 Similar to
<em>zebra
</em>, but additional dimming of uninteresting parts
2602 of moved code is performed. The bordering lines of two adjacent
2603 blocks are considered interesting, the rest is uninteresting.
2604 <code>dimmed_zebra
</code> is a deprecated synonym.
2610 <dt class=
"hdlist1">
2615 Turn off move detection. This can be used to override configuration
2616 settings. It is the same as
<code>--color-moved=no
</code>.
2619 <dt class=
"hdlist1">
2620 --color-moved-ws=
<modes
>
2624 This configures how whitespace is ignored when performing the
2625 move detection for
<code>--color-moved
</code>.
2626 These modes can be given as a comma separated list:
2628 <div class=
"openblock">
2629 <div class=
"content">
2630 <div class=
"dlist"><dl>
2631 <dt class=
"hdlist1">
2636 Do not ignore whitespace when performing move detection.
2639 <dt class=
"hdlist1">
2644 Ignore changes in whitespace at EOL.
2647 <dt class=
"hdlist1">
2652 Ignore changes in amount of whitespace. This ignores whitespace
2653 at line end, and considers all other sequences of one or
2654 more whitespace characters to be equivalent.
2657 <dt class=
"hdlist1">
2662 Ignore whitespace when comparing lines. This ignores differences
2663 even if one line has whitespace where the other line has none.
2666 <dt class=
"hdlist1">
2667 allow-indentation-change
2671 Initially ignore any whitespace in the move detection, then
2672 group the moved code blocks only into a block if the change in
2673 whitespace is the same per line. This is incompatible with the
2680 <dt class=
"hdlist1">
2685 Do not ignore whitespace when performing move detection. This can be
2686 used to override configuration settings. It is the same as
2687 <code>--color-moved-ws=no
</code>.
2690 <dt class=
"hdlist1">
2691 --word-diff[=
<mode
>]
2695 Show a word diff, using the
<mode
> to delimit changed words.
2696 By default, words are delimited by whitespace; see
2697 <code>--word-diff-regex
</code> below. The
<mode
> defaults to
<em>plain
</em>, and
2700 <div class=
"openblock">
2701 <div class=
"content">
2702 <div class=
"dlist"><dl>
2703 <dt class=
"hdlist1">
2708 Highlight changed words using only colors. Implies
<code>--color
</code>.
2711 <dt class=
"hdlist1">
2716 Show words as
<code>[-removed-]
</code> and
<code>{+added+}
</code>. Makes no
2717 attempts to escape the delimiters if they appear in the input,
2718 so the output may be ambiguous.
2721 <dt class=
"hdlist1">
2726 Use a special line-based format intended for script
2727 consumption. Added/removed/unchanged runs are printed in the
2728 usual unified diff format, starting with a
<code>+
</code>/
<code>-
</code>/` `
2729 character at the beginning of the line and extending to the
2730 end of the line. Newlines in the input are represented by a
2731 tilde
<code>~
</code> on a line of its own.
2734 <dt class=
"hdlist1">
2739 Disable word diff again.
2744 <div class=
"paragraph"><p>Note that despite the name of the first mode, color is used to
2745 highlight the changed parts in all modes if enabled.
</p></div>
2747 <dt class=
"hdlist1">
2748 --word-diff-regex=
<regex
>
2752 Use
<regex
> to decide what a word is, instead of considering
2753 runs of non-whitespace to be a word. Also implies
2754 <code>--word-diff
</code> unless it was already enabled.
2756 <div class=
"paragraph"><p>Every non-overlapping match of the
2757 <regex
> is considered a word. Anything between these matches is
2758 considered whitespace and ignored(!) for the purposes of finding
2759 differences. You may want to append
<code>|[^[:space:]]
</code> to your regular
2760 expression to make sure that it matches all non-whitespace characters.
2761 A match that contains a newline is silently truncated(!) at the
2763 <div class=
"paragraph"><p>For example,
<code>--word-diff-regex=.
</code> will treat each character as a word
2764 and, correspondingly, show differences character by character.
</p></div>
2765 <div class=
"paragraph"><p>The regex can also be set via a diff driver or configuration option, see
2766 <a href=
"gitattributes.html">gitattributes(
5)
</a> or
<a href=
"git-config.html">git-config(
1)
</a>. Giving it explicitly
2767 overrides any diff driver or configuration setting. Diff drivers
2768 override configuration settings.
</p></div>
2770 <dt class=
"hdlist1">
2771 --color-words[=
<regex
>]
2775 Equivalent to
<code>--word-diff=color
</code> plus (if a regex was
2776 specified)
<code>--word-diff-regex=
<regex
></code>.
2779 <dt class=
"hdlist1">
2784 Turn off rename detection, even when the configuration
2785 file gives the default to do so.
2788 <dt class=
"hdlist1">
2793 Whether to use empty blobs as rename source.
2796 <dt class=
"hdlist1">
2801 Warn if changes introduce conflict markers or whitespace errors.
2802 What are considered whitespace errors is controlled by
<code>core.whitespace
</code>
2803 configuration. By default, trailing whitespaces (including
2804 lines that consist solely of whitespaces) and a space character
2805 that is immediately followed by a tab character inside the
2806 initial indent of the line are considered whitespace errors.
2807 Exits with non-zero status if problems are found. Not compatible
2811 <dt class=
"hdlist1">
2812 --ws-error-highlight=
<kind
>
2816 Highlight whitespace errors in the
<code>context
</code>,
<code>old
</code> or
<code>new
</code>
2817 lines of the diff. Multiple values are separated by comma,
2818 <code>none
</code> resets previous values,
<code>default
</code> reset the list to
2819 <code>new
</code> and
<code>all
</code> is a shorthand for
<code>old,new,context
</code>. When
2820 this option is not given, and the configuration variable
2821 <code>diff.wsErrorHighlight
</code> is not set, only whitespace errors in
2822 <code>new
</code> lines are highlighted. The whitespace errors are colored
2823 with
<code>color.diff.whitespace
</code>.
2826 <dt class=
"hdlist1">
2831 Instead of the first handful of characters, show the full
2832 pre- and post-image blob object names on the
"index"
2833 line when generating patch format output.
2836 <dt class=
"hdlist1">
2841 In addition to
<code>--full-index
</code>, output a binary diff that
2842 can be applied with
<code>git-apply
</code>.
2843 Implies
<code>--patch
</code>.
2846 <dt class=
"hdlist1">
2847 --abbrev[=
<n
>]
2851 Instead of showing the full
40-byte hexadecimal object
2852 name in diff-raw format output and diff-tree header
2853 lines, show the shortest prefix that is at least
<em><n
></em>
2854 hexdigits long that uniquely refers the object.
2855 In diff-patch output format,
<code>--full-index
</code> takes higher
2856 precedence, i.e. if
<code>--full-index
</code> is specified, full blob
2857 names will be shown regardless of
<code>--abbrev
</code>.
2858 Non default number of digits can be specified with
<code>--abbrev=
<n
></code>.
2861 <dt class=
"hdlist1">
2862 -B[
<n
>][/
<m
>]
2864 <dt class=
"hdlist1">
2865 --break-rewrites[=[
<n
>][/
<m
>]]
2869 Break complete rewrite changes into pairs of delete and
2870 create. This serves two purposes:
2872 <div class=
"paragraph"><p>It affects the way a change that amounts to a total rewrite of a file
2873 not as a series of deletion and insertion mixed together with a very
2874 few lines that happen to match textually as the context, but as a
2875 single deletion of everything old followed by a single insertion of
2876 everything new, and the number
<code>m
</code> controls this aspect of the -B
2877 option (defaults to
60%).
<code>-B/
70%
</code> specifies that less than
30% of the
2878 original should remain in the result for Git to consider it a total
2879 rewrite (i.e. otherwise the resulting patch will be a series of
2880 deletion and insertion mixed together with context lines).
</p></div>
2881 <div class=
"paragraph"><p>When used with -M, a totally-rewritten file is also considered as the
2882 source of a rename (usually -M only considers a file that disappeared
2883 as the source of a rename), and the number
<code>n
</code> controls this aspect of
2884 the -B option (defaults to
50%).
<code>-B20%
</code> specifies that a change with
2885 addition and deletion compared to
20% or more of the file
’s size are
2886 eligible for being picked up as a possible source of a rename to
2887 another file.
</p></div>
2889 <dt class=
"hdlist1">
2892 <dt class=
"hdlist1">
2893 --find-renames[=
<n
>]
2897 If generating diffs, detect and report renames for each commit.
2898 For following files across renames while traversing history, see
2899 <code>--follow
</code>.
2900 If
<code>n
</code> is specified, it is a threshold on the similarity
2901 index (i.e. amount of addition/deletions compared to the
2902 file
’s size). For example,
<code>-M90%
</code> means Git should consider a
2903 delete/add pair to be a rename if more than
90% of the file
2904 hasn
’t changed. Without a
<code>%
</code> sign, the number is to be read as
2905 a fraction, with a decimal point before it. I.e.,
<code>-M5
</code> becomes
2906 0.5, and is thus the same as
<code>-M50%
</code>. Similarly,
<code>-M05
</code> is
2907 the same as
<code>-M5%
</code>. To limit detection to exact renames, use
2908 <code>-M100%
</code>. The default similarity index is
50%.
2911 <dt class=
"hdlist1">
2914 <dt class=
"hdlist1">
2915 --find-copies[=
<n
>]
2919 Detect copies as well as renames. See also
<code>--find-copies-harder
</code>.
2920 If
<code>n
</code> is specified, it has the same meaning as for
<code>-M
<n
></code>.
2923 <dt class=
"hdlist1">
2924 --find-copies-harder
2928 For performance reasons, by default,
<code>-C
</code> option finds copies only
2929 if the original file of the copy was modified in the same
2930 changeset. This flag makes the command
2931 inspect unmodified files as candidates for the source of
2932 copy. This is a very expensive operation for large
2933 projects, so use it with caution. Giving more than one
2934 <code>-C
</code> option has the same effect.
2937 <dt class=
"hdlist1">
2940 <dt class=
"hdlist1">
2941 --irreversible-delete
2945 Omit the preimage for deletes, i.e. print only the header but not
2946 the diff between the preimage and
<code>/dev/null
</code>. The resulting patch
2947 is not meant to be applied with
<code>patch
</code> or
<code>git apply
</code>; this is
2948 solely for people who want to just concentrate on reviewing the
2949 text after the change. In addition, the output obviously lacks
2950 enough information to apply such a patch in reverse, even manually,
2951 hence the name of the option.
2953 <div class=
"paragraph"><p>When used together with
<code>-B
</code>, omit also the preimage in the deletion part
2954 of a delete/create pair.
</p></div>
2956 <dt class=
"hdlist1">
2961 The
<code>-M
</code> and
<code>-C
</code> options involve some preliminary steps that
2962 can detect subsets of renames/copies cheaply, followed by an
2963 exhaustive fallback portion that compares all remaining
2964 unpaired destinations to all relevant sources. (For renames,
2965 only remaining unpaired sources are relevant; for copies, all
2966 original sources are relevant.) For N sources and
2967 destinations, this exhaustive check is O(N^
2). This option
2968 prevents the exhaustive portion of rename/copy detection from
2969 running if the number of source/destination files involved
2970 exceeds the specified number. Defaults to diff.renameLimit.
2971 Note that a value of
0 is treated as unlimited.
2974 <dt class=
"hdlist1">
2975 --diff-filter=[(A|C|D|M|R|T|U|X|B)
…[*]]
2979 Select only files that are Added (
<code>A
</code>), Copied (
<code>C
</code>),
2980 Deleted (
<code>D
</code>), Modified (
<code>M
</code>), Renamed (
<code>R
</code>), have their
2981 type (i.e. regular file, symlink, submodule,
…) changed (
<code>T
</code>),
2982 are Unmerged (
<code>U
</code>), are
2983 Unknown (
<code>X
</code>), or have had their pairing Broken (
<code>B
</code>).
2984 Any combination of the filter characters (including none) can be used.
2985 When
<code>*
</code> (All-or-none) is added to the combination, all
2986 paths are selected if there is any file that matches
2987 other criteria in the comparison; if there is no file
2988 that matches other criteria, nothing is selected.
2990 <div class=
"paragraph"><p>Also, these upper-case letters can be downcased to exclude. E.g.
2991 <code>--diff-filter=ad
</code> excludes added and deleted paths.
</p></div>
2992 <div class=
"paragraph"><p>Note that not all diffs can feature all types. For instance, copied and
2993 renamed entries cannot appear if detection for those types is disabled.
</p></div>
2995 <dt class=
"hdlist1">
3000 Look for differences that change the number of occurrences of
3001 the specified string (i.e. addition/deletion) in a file.
3002 Intended for the scripter
’s use.
3004 <div class=
"paragraph"><p>It is useful when you
’re looking for an exact block of code (like a
3005 struct), and want to know the history of that block since it first
3006 came into being: use the feature iteratively to feed the interesting
3007 block in the preimage back into
<code>-S
</code>, and keep going until you get the
3008 very first version of the block.
</p></div>
3009 <div class=
"paragraph"><p>Binary files are searched as well.
</p></div>
3011 <dt class=
"hdlist1">
3016 Look for differences whose patch text contains added/removed
3017 lines that match
<regex
>.
3019 <div class=
"paragraph"><p>To illustrate the difference between
<code>-S
<regex
> --pickaxe-regex
</code> and
3020 <code>-G
<regex
></code>, consider a commit with the following diff in the same
3022 <div class=
"listingblock">
3023 <div class=
"content">
3024 <pre><code>+ return frotz(nitfol, two-
>ptr,
1,
0);
3026 - hit = frotz(nitfol, mf2.ptr,
1,
0);
</code></pre>
3028 <div class=
"paragraph"><p>While
<code>git log -G
"frotz\(nitfol"</code> will show this commit,
<code>git log
3029 -S
"frotz\(nitfol" --pickaxe-regex
</code> will not (because the number of
3030 occurrences of that string did not change).
</p></div>
3031 <div class=
"paragraph"><p>Unless
<code>--text
</code> is supplied patches of binary files without a textconv
3032 filter will be ignored.
</p></div>
3033 <div class=
"paragraph"><p>See the
<em>pickaxe
</em> entry in
<a href=
"gitdiffcore.html">gitdiffcore(
7)
</a> for more
3034 information.
</p></div>
3036 <dt class=
"hdlist1">
3037 --find-object=
<object-id
>
3041 Look for differences that change the number of occurrences of
3042 the specified object. Similar to
<code>-S
</code>, just the argument is different
3043 in that it doesn
’t search for a specific string but for a specific
3046 <div class=
"paragraph"><p>The object can be a blob or a submodule commit. It implies the
<code>-t
</code> option in
3047 <code>git-log
</code> to also find trees.
</p></div>
3049 <dt class=
"hdlist1">
3054 When
<code>-S
</code> or
<code>-G
</code> finds a change, show all the changes in that
3055 changeset, not just the files that contain the change
3059 <dt class=
"hdlist1">
3064 Treat the
<string
> given to
<code>-S
</code> as an extended POSIX regular
3065 expression to match.
3068 <dt class=
"hdlist1">
3073 Control the order in which files appear in the output.
3074 This overrides the
<code>diff.orderFile
</code> configuration variable
3075 (see
<a href=
"git-config.html">git-config(
1)
</a>). To cancel
<code>diff.orderFile
</code>,
3076 use
<code>-O/dev/null
</code>.
3078 <div class=
"paragraph"><p>The output order is determined by the order of glob patterns in
3080 All files with pathnames that match the first pattern are output
3081 first, all files with pathnames that match the second pattern (but not
3082 the first) are output next, and so on.
3083 All files with pathnames that do not match any pattern are output
3084 last, as if there was an implicit match-all pattern at the end of the
3086 If multiple pathnames have the same rank (they match the same pattern
3087 but no earlier patterns), their output order relative to each other is
3088 the normal order.
</p></div>
3089 <div class=
"paragraph"><p><orderfile
> is parsed as follows:
</p></div>
3090 <div class=
"openblock">
3091 <div class=
"content">
3092 <div class=
"ulist"><ul>
3095 Blank lines are ignored, so they can be used as separators for
3101 Lines starting with a hash (
"<code>#</code>") are ignored, so they can be used
3102 for comments. Add a backslash (
"<code>\</code>") to the beginning of the
3103 pattern if it starts with a hash.
3108 Each other line contains a single pattern.
3113 <div class=
"paragraph"><p>Patterns have the same syntax and semantics as patterns used for
3114 fnmatch(
3) without the FNM_PATHNAME flag, except a pathname also
3115 matches a pattern if removing any number of the final pathname
3116 components matches the pattern. For example, the pattern
"<code>foo*bar</code>"
3117 matches
"<code>fooasdfbar</code>" and
"<code>foo/bar/baz/asdf</code>" but not
"<code>foobarx</code>".
</p></div>
3119 <dt class=
"hdlist1">
3120 --skip-to=
<file
>
3122 <dt class=
"hdlist1">
3123 --rotate-to=
<file
>
3127 Discard the files before the named
<file
> from the output
3128 (i.e.
<em>skip to
</em>), or move them to the end of the output
3129 (i.e.
<em>rotate to
</em>). These were invented primarily for use
3130 of the
<code>git difftool
</code> command, and may not be very useful
3134 <dt class=
"hdlist1">
3139 Swap two inputs; that is, show differences from index or
3140 on-disk file to tree contents.
3143 <dt class=
"hdlist1">
3144 --relative[=
<path
>]
3146 <dt class=
"hdlist1">
3151 When run from a subdirectory of the project, it can be
3152 told to exclude changes outside the directory and show
3153 pathnames relative to it with this option. When you are
3154 not in a subdirectory (e.g. in a bare repository), you
3155 can name which subdirectory to make the output relative
3156 to by giving a
<path
> as an argument.
3157 <code>--no-relative
</code> can be used to countermand both
<code>diff.relative
</code> config
3158 option and previous
<code>--relative
</code>.
3161 <dt class=
"hdlist1">
3164 <dt class=
"hdlist1">
3169 Treat all files as text.
3172 <dt class=
"hdlist1">
3177 Ignore carriage-return at the end of line when doing a comparison.
3180 <dt class=
"hdlist1">
3181 --ignore-space-at-eol
3185 Ignore changes in whitespace at EOL.
3188 <dt class=
"hdlist1">
3191 <dt class=
"hdlist1">
3192 --ignore-space-change
3196 Ignore changes in amount of whitespace. This ignores whitespace
3197 at line end, and considers all other sequences of one or
3198 more whitespace characters to be equivalent.
3201 <dt class=
"hdlist1">
3204 <dt class=
"hdlist1">
3209 Ignore whitespace when comparing lines. This ignores
3210 differences even if one line has whitespace where the other
3214 <dt class=
"hdlist1">
3215 --ignore-blank-lines
3219 Ignore changes whose lines are all blank.
3222 <dt class=
"hdlist1">
3225 <dt class=
"hdlist1">
3226 --ignore-matching-lines=
<regex
>
3230 Ignore changes whose all lines match
<regex
>. This option may
3231 be specified more than once.
3234 <dt class=
"hdlist1">
3235 --inter-hunk-context=
<lines
>
3239 Show the context between diff hunks, up to the specified number
3240 of lines, thereby fusing hunks that are close to each other.
3241 Defaults to
<code>diff.interHunkContext
</code> or
0 if the config option
3245 <dt class=
"hdlist1">
3248 <dt class=
"hdlist1">
3253 Show whole function as context lines for each change.
3254 The function names are determined in the same way as
3255 <code>git diff
</code> works out patch hunk headers (see
<em>Defining a
3256 custom hunk-header
</em> in
<a href=
"gitattributes.html">gitattributes(
5)
</a>).
3259 <dt class=
"hdlist1">
3264 Allow an external diff helper to be executed. If you set an
3265 external diff driver with
<a href=
"gitattributes.html">gitattributes(
5)
</a>, you need
3266 to use this option with
<a href=
"git-log.html">git-log(
1)
</a> and friends.
3269 <dt class=
"hdlist1">
3274 Disallow external diff drivers.
3277 <dt class=
"hdlist1">
3280 <dt class=
"hdlist1">
3285 Allow (or disallow) external text conversion filters to be run
3286 when comparing binary files. See
<a href=
"gitattributes.html">gitattributes(
5)
</a> for
3287 details. Because textconv filters are typically a one-way
3288 conversion, the resulting diff is suitable for human
3289 consumption, but cannot be applied. For this reason, textconv
3290 filters are enabled by default only for
<a href=
"git-diff.html">git-diff(
1)
</a> and
3291 <a href=
"git-log.html">git-log(
1)
</a>, but not for
<a href=
"git-format-patch.html">git-format-patch(
1)
</a> or
3292 diff plumbing commands.
3295 <dt class=
"hdlist1">
3296 --ignore-submodules[=
<when
>]
3300 Ignore changes to submodules in the diff generation.
<when
> can be
3301 either
"none",
"untracked",
"dirty" or
"all", which is the default.
3302 Using
"none" will consider the submodule modified when it either contains
3303 untracked or modified files or its HEAD differs from the commit recorded
3304 in the superproject and can be used to override any settings of the
3305 <em>ignore
</em> option in
<a href=
"git-config.html">git-config(
1)
</a> or
<a href=
"gitmodules.html">gitmodules(
5)
</a>. When
3306 "untracked" is used submodules are not considered dirty when they only
3307 contain untracked content (but they are still scanned for modified
3308 content). Using
"dirty" ignores all changes to the work tree of submodules,
3309 only changes to the commits stored in the superproject are shown (this was
3310 the behavior until
1.7.0). Using
"all" hides all changes to submodules.
3313 <dt class=
"hdlist1">
3314 --src-prefix=
<prefix
>
3318 Show the given source prefix instead of
"a/".
3321 <dt class=
"hdlist1">
3322 --dst-prefix=
<prefix
>
3326 Show the given destination prefix instead of
"b/".
3329 <dt class=
"hdlist1">
3334 Do not show any source or destination prefix.
3337 <dt class=
"hdlist1">
3342 Use the default source and destination prefixes (
"a/" and
"b/").
3343 This is usually the default already, but may be used to override
3344 config such as
<code>diff.noprefix
</code>.
3347 <dt class=
"hdlist1">
3348 --line-prefix=
<prefix
>
3352 Prepend an additional prefix to every line of output.
3355 <dt class=
"hdlist1">
3356 --ita-invisible-in-index
3360 By default entries added by
"git add -N" appear as an existing
3361 empty file in
"git diff" and a new file in
"git diff --cached".
3362 This option makes the entry appear as a new file in
"git diff"
3363 and non-existent in
"git diff --cached". This option could be
3364 reverted with
<code>--ita-visible-in-index
</code>. Both options are
3365 experimental and could be removed in future.
3369 <div class=
"paragraph"><p>For more detailed explanation on these common options, see also
3370 <a href=
"gitdiffcore.html">gitdiffcore(
7)
</a>.
</p></div>
3374 <h2 id=
"generate_patch_text_with_p">Generating patch text with -p
</h2>
3375 <div class=
"sectionbody">
3376 <div class=
"paragraph"><p>Running
3377 <a href=
"git-diff.html">git-diff(
1)
</a>,
3378 <a href=
"git-log.html">git-log(
1)
</a>,
3379 <a href=
"git-show.html">git-show(
1)
</a>,
3380 <a href=
"git-diff-index.html">git-diff-index(
1)
</a>,
3381 <a href=
"git-diff-tree.html">git-diff-tree(
1)
</a>, or
3382 <a href=
"git-diff-files.html">git-diff-files(
1)
</a>
3383 with the
<code>-p
</code> option produces patch text.
3384 You can customize the creation of patch text via the
3385 <code>GIT_EXTERNAL_DIFF
</code> and the
<code>GIT_DIFF_OPTS
</code> environment variables
3386 (see
<a href=
"git.html">git(
1)
</a>), and the
<code>diff
</code> attribute (see
<a href=
"gitattributes.html">gitattributes(
5)
</a>).
</p></div>
3387 <div class=
"paragraph"><p>What the -p option produces is slightly different from the traditional
3388 diff format:
</p></div>
3389 <div class=
"olist arabic"><ol class=
"arabic">
3392 It is preceded with a
"git diff" header that looks like this:
3394 <div class=
"literalblock">
3395 <div class=
"content">
3396 <pre><code>diff --git a/file1 b/file2
</code></pre>
3398 <div class=
"paragraph"><p>The
<code>a/
</code> and
<code>b/
</code> filenames are the same unless rename/copy is
3399 involved. Especially, even for a creation or a deletion,
3400 <code>/dev/null
</code> is
<em>not
</em> used in place of the
<code>a/
</code> or
<code>b/
</code> filenames.
</p></div>
3401 <div class=
"paragraph"><p>When rename/copy is involved,
<code>file1
</code> and
<code>file2
</code> show the
3402 name of the source file of the rename/copy and the name of
3403 the file that rename/copy produces, respectively.
</p></div>
3407 It is followed by one or more extended header lines:
3409 <div class=
"literalblock">
3410 <div class=
"content">
3411 <pre><code>old mode
<mode
>
3412 new mode
<mode
>
3413 deleted file mode
<mode
>
3414 new file mode
<mode
>
3415 copy from
<path
>
3416 copy to
<path
>
3417 rename from
<path
>
3418 rename to
<path
>
3419 similarity index
<number
>
3420 dissimilarity index
<number
>
3421 index
<hash
>..
<hash
> <mode
></code></pre>
3423 <div class=
"paragraph"><p>File modes are printed as
6-digit octal numbers including the file type
3424 and file permission bits.
</p></div>
3425 <div class=
"paragraph"><p>Path names in extended headers do not include the
<code>a/
</code> and
<code>b/
</code> prefixes.
</p></div>
3426 <div class=
"paragraph"><p>The similarity index is the percentage of unchanged lines, and
3427 the dissimilarity index is the percentage of changed lines. It
3428 is a rounded down integer, followed by a percent sign. The
3429 similarity index value of
100% is thus reserved for two equal
3430 files, while
100% dissimilarity means that no line from the old
3431 file made it into the new one.
</p></div>
3432 <div class=
"paragraph"><p>The index line includes the blob object names before and after the change.
3433 The
<mode
> is included if the file mode does not change; otherwise,
3434 separate lines indicate the old and the new mode.
</p></div>
3438 Pathnames with
"unusual" characters are quoted as explained for
3439 the configuration variable
<code>core.quotePath
</code> (see
3440 <a href=
"git-config.html">git-config(
1)
</a>).
3445 All the
<code>file1
</code> files in the output refer to files before the
3446 commit, and all the
<code>file2
</code> files refer to files after the commit.
3447 It is incorrect to apply each change to each file sequentially. For
3448 example, this patch will swap a and b:
3450 <div class=
"literalblock">
3451 <div class=
"content">
3452 <pre><code>diff --git a/a b/b
3457 rename to a
</code></pre>
3462 Hunk headers mention the name of the function to which the hunk
3463 applies. See
"Defining a custom hunk-header" in
3464 <a href=
"gitattributes.html">gitattributes(
5)
</a> for details of how to tailor to this to
3472 <h2 id=
"_combined_diff_format">Combined diff format
</h2>
3473 <div class=
"sectionbody">
3474 <div class=
"paragraph"><p>Any diff-generating command can take the
<code>-c
</code> or
<code>--cc
</code> option to
3475 produce a
<em>combined diff
</em> when showing a merge. This is the default
3476 format when showing merges with
<a href=
"git-diff.html">git-diff(
1)
</a> or
3477 <a href=
"git-show.html">git-show(
1)
</a>. Note also that you can give suitable
3478 <code>--diff-merges
</code> option to any of these commands to force generation of
3479 diffs in specific format.
</p></div>
3480 <div class=
"paragraph"><p>A
"combined diff" format looks like this:
</p></div>
3481 <div class=
"listingblock">
3482 <div class=
"content">
3483 <pre><code>diff --combined describe.c
3484 index fabadb8,cc95eb0.
.4866510
3487 @@@ -
98,
20 -
98,
12 +
98,
20 @@@
3488 return (a_date
> b_date) ? -
1 : (a_date == b_date) ?
0 :
1;
3491 - static void describe(char *arg)
3492 -static void describe(struct commit *cmit, int last_one)
3493 ++static void describe(char *arg, int last_one)
3495 + unsigned char sha1[
20];
3496 + struct commit *cmit;
3497 struct commit_list *list;
3498 static int initialized =
0;
3499 struct commit_name *n;
3501 + if (get_sha1(arg, sha1)
< 0)
3502 + usage(describe_usage);
3503 + cmit = lookup_commit_reference(sha1);
3505 + usage(describe_usage);
3509 for_each_ref(get_name);
</code></pre>
3511 <div class=
"olist arabic"><ol class=
"arabic">
3514 It is preceded with a
"git diff" header, that looks like
3515 this (when the
<code>-c
</code> option is used):
3517 <div class=
"literalblock">
3518 <div class=
"content">
3519 <pre><code>diff --combined file
</code></pre>
3521 <div class=
"paragraph"><p>or like this (when the
<code>--cc
</code> option is used):
</p></div>
3522 <div class=
"literalblock">
3523 <div class=
"content">
3524 <pre><code>diff --cc file
</code></pre>
3529 It is followed by one or more extended header lines
3530 (this example shows a merge with two parents):
3532 <div class=
"literalblock">
3533 <div class=
"content">
3534 <pre><code>index
<hash
>,
<hash
>..
<hash
>
3535 mode
<mode
>,
<mode
>..
<mode
>
3536 new file mode
<mode
>
3537 deleted file mode
<mode
>,
<mode
></code></pre>
3539 <div class=
"paragraph"><p>The
<code>mode
<mode
>,
<mode
>..
<mode
></code> line appears only if at least one of
3540 the
<mode
> is different from the rest. Extended headers with
3541 information about detected contents movement (renames and
3542 copying detection) are designed to work with diff of two
3543 <tree-ish
> and are not used by combined diff format.
</p></div>
3547 It is followed by two-line from-file/to-file header
3549 <div class=
"literalblock">
3550 <div class=
"content">
3551 <pre><code>--- a/file
3552 +++ b/file
</code></pre>
3554 <div class=
"paragraph"><p>Similar to two-line header for traditional
<em>unified
</em> diff
3555 format,
<code>/dev/null
</code> is used to signal created or deleted
3557 <div class=
"paragraph"><p>However, if the --combined-all-paths option is provided, instead of a
3558 two-line from-file/to-file you get a N+
1 line from-file/to-file header,
3559 where N is the number of parents in the merge commit
</p></div>
3560 <div class=
"literalblock">
3561 <div class=
"content">
3562 <pre><code>--- a/file
3565 +++ b/file
</code></pre>
3567 <div class=
"paragraph"><p>This extended format can be useful if rename or copy detection is
3568 active, to allow you to see the original name of the file in different
3573 Chunk header format is modified to prevent people from
3574 accidentally feeding it to
<code>patch -p1
</code>. Combined diff format
3575 was created for review of merge commit changes, and was not
3576 meant to be applied. The change is similar to the change in the
3577 extended
<em>index
</em> header:
3579 <div class=
"literalblock">
3580 <div class=
"content">
3581 <pre><code>@@@
<from-file-range
> <from-file-range
> <to-file-range
> @@@
</code></pre>
3583 <div class=
"paragraph"><p>There are (number of parents +
1)
<code>@
</code> characters in the chunk
3584 header for combined diff format.
</p></div>
3587 <div class=
"paragraph"><p>Unlike the traditional
<em>unified
</em> diff format, which shows two
3588 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
3589 added to B), or
<code>" "</code> (space
 — unchanged) prefix, this format
3590 compares two or more files file1, file2,
… with one file X, and
3591 shows how X differs from each of fileN. One column for each of
3592 fileN is prepended to the output line to note how X
’s line is
3593 different from it.
</p></div>
3594 <div class=
"paragraph"><p>A
<code>-
</code> character in the column N means that the line appears in
3595 fileN but it does not appear in the result. A
<code>+
</code> character
3596 in the column N means that the line appears in the result,
3597 and fileN does not have that line (in other words, the line was
3598 added, from the point of view of that parent).
</p></div>
3599 <div class=
"paragraph"><p>In the above example output, the function signature was changed
3600 from both files (hence two
<code>-
</code> removals from both file1 and
3601 file2, plus
<code>++
</code> to mean one line that was added does not appear
3602 in either file1 or file2). Also eight other lines are the same
3603 from file1 but do not appear in file2 (hence prefixed with
<code>+
</code>).
</p></div>
3604 <div class=
"paragraph"><p>When shown by
<code>git diff-tree -c
</code>, it compares the parents of a
3605 merge commit with the merge result (i.e. file1..fileN are the
3606 parents). When shown by
<code>git diff-files -c
</code>, it compares the
3607 two unresolved merge parents with the working tree file
3608 (i.e. file1 is stage
2 aka
"our version", file2 is stage
3 aka
3609 "their version").
</p></div>
3613 <h2 id=
"_examples">EXAMPLES
</h2>
3614 <div class=
"sectionbody">
3615 <div class=
"dlist"><dl>
3616 <dt class=
"hdlist1">
3617 <code>git show v1.0
.0</code>
3621 Shows the tag
<code>v1.0
.0</code>, along with the object the tags
3625 <dt class=
"hdlist1">
3626 <code>git show v1.0
.0^{tree}
</code>
3630 Shows the tree pointed to by the tag
<code>v1.0
.0</code>.
3633 <dt class=
"hdlist1">
3634 <code>git show -s --format=%s v1.0
.0^{commit}
</code>
3638 Shows the subject of the commit pointed to by the
3639 tag
<code>v1.0
.0</code>.
3642 <dt class=
"hdlist1">
3643 <code>git show next~
10:Documentation/README
</code>
3647 Shows the contents of the file
<code>Documentation/README
</code> as
3648 they were current in the
10th last commit of the branch
3652 <dt class=
"hdlist1">
3653 <code>git show master:Makefile master:t/Makefile
</code>
3657 Concatenates the contents of said Makefiles in the head
3658 of the branch
<code>master
</code>.
3665 <h2 id=
"_discussion">DISCUSSION
</h2>
3666 <div class=
"sectionbody">
3667 <div class=
"paragraph"><p>Git is to some extent character encoding agnostic.
</p></div>
3668 <div class=
"ulist"><ul>
3671 The contents of the blob objects are uninterpreted sequences
3672 of bytes. There is no encoding translation at the core
3678 Path names are encoded in UTF-
8 normalization form C. This
3679 applies to tree objects, the index file, ref names, as well as
3680 path names in command line arguments, environment variables
3681 and config files (
<code>.git/config
</code> (see
<a href=
"git-config.html">git-config(
1)
</a>),
3682 <a href=
"gitignore.html">gitignore(
5)
</a>,
<a href=
"gitattributes.html">gitattributes(
5)
</a> and
3683 <a href=
"gitmodules.html">gitmodules(
5)
</a>).
3685 <div class=
"paragraph"><p>Note that Git at the core level treats path names simply as
3686 sequences of non-NUL bytes, there are no path name encoding
3687 conversions (except on Mac and Windows). Therefore, using
3688 non-ASCII path names will mostly work even on platforms and file
3689 systems that use legacy extended ASCII encodings. However,
3690 repositories created on such systems will not work properly on
3691 UTF-
8-based systems (e.g. Linux, Mac, Windows) and vice versa.
3692 Additionally, many Git-based tools simply assume path names to
3693 be UTF-
8 and will fail to display other encodings correctly.
</p></div>
3697 Commit log messages are typically encoded in UTF-
8, but other
3698 extended ASCII encodings are also supported. This includes
3699 ISO-
8859-x, CP125x and many others, but
<em>not
</em> UTF-
16/
32,
3700 EBCDIC and CJK multi-byte encodings (GBK, Shift-JIS, Big5,
3705 <div class=
"paragraph"><p>Although we encourage that the commit log messages are encoded
3706 in UTF-
8, both the core and Git Porcelain are designed not to
3707 force UTF-
8 on projects. If all participants of a particular
3708 project find it more convenient to use legacy encodings, Git
3709 does not forbid it. However, there are a few things to keep in
3711 <div class=
"olist arabic"><ol class=
"arabic">
3714 <em>git commit
</em> and
<em>git commit-tree
</em> issues
3715 a warning if the commit log message given to it does not look
3716 like a valid UTF-
8 string, unless you explicitly say your
3717 project uses a legacy encoding. The way to say this is to
3718 have
<code>i18n.commitEncoding
</code> in
<code>.git/config
</code> file, like this:
3720 <div class=
"listingblock">
3721 <div class=
"content">
3723 commitEncoding = ISO-
8859-
1</code></pre>
3725 <div class=
"paragraph"><p>Commit objects created with the above setting record the value
3726 of
<code>i18n.commitEncoding
</code> in its
<code>encoding
</code> header. This is to
3727 help other people who look at them later. Lack of this header
3728 implies that the commit log message is encoded in UTF-
8.
</p></div>
3732 <em>git log
</em>,
<em>git show
</em>,
<em>git blame
</em> and friends look at the
3733 <code>encoding
</code> header of a commit object, and try to re-code the
3734 log message into UTF-
8 unless otherwise specified. You can
3735 specify the desired output encoding with
3736 <code>i18n.logOutputEncoding
</code> in
<code>.git/config
</code> file, like this:
3738 <div class=
"listingblock">
3739 <div class=
"content">
3741 logOutputEncoding = ISO-
8859-
1</code></pre>
3743 <div class=
"paragraph"><p>If you do not have this configuration variable, the value of
3744 <code>i18n.commitEncoding
</code> is used instead.
</p></div>
3747 <div class=
"paragraph"><p>Note that we deliberately chose not to re-code the commit log
3748 message when a commit is made to force UTF-
8 at the commit
3749 object level, because re-coding to UTF-
8 is not necessarily a
3750 reversible operation.
</p></div>
3754 <h2 id=
"_git">GIT
</h2>
3755 <div class=
"sectionbody">
3756 <div class=
"paragraph"><p>Part of the
<a href=
"git.html">git(
1)
</a> suite
</p></div>
3760 <div id=
"footnotes"><hr /></div>
3762 <div id=
"footer-text">
3764 2021-
02-
05 22:
36:
43 PST