Autogenerated HTML docs for v2.42.0-398-ga9ecd
[git-htmldocs.git] / git-cat-file.html
blob7a4c57cb603ffd092e3a18f2c3b85b15dbce2f03
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">
5 <head>
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-cat-file(1)</title>
9 <style type="text/css">
10 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
12 /* Default font. */
13 body {
14 font-family: Georgia,serif;
17 /* Title font. */
18 h1, h2, h3, h4, h5, h6,
19 div.title, caption.title,
20 thead, p.table.header,
21 #toctitle,
22 #author, #revnumber, #revdate, #revremark,
23 #footer {
24 font-family: Arial,Helvetica,sans-serif;
27 body {
28 margin: 1em 5% 1em 5%;
31 a {
32 color: blue;
33 text-decoration: underline;
35 a:visited {
36 color: fuchsia;
39 em {
40 font-style: italic;
41 color: navy;
44 strong {
45 font-weight: bold;
46 color: #083194;
49 h1, h2, h3, h4, h5, h6 {
50 color: #527bbd;
51 margin-top: 1.2em;
52 margin-bottom: 0.5em;
53 line-height: 1.3;
56 h1, h2, h3 {
57 border-bottom: 2px solid silver;
59 h2 {
60 padding-top: 0.5em;
62 h3 {
63 float: left;
65 h3 + * {
66 clear: left;
68 h5 {
69 font-size: 1.0em;
72 div.sectionbody {
73 margin-left: 0;
76 hr {
77 border: 1px solid silver;
80 p {
81 margin-top: 0.5em;
82 margin-bottom: 0.5em;
85 ul, ol, li > p {
86 margin-top: 0;
88 ul > li { color: #aaa; }
89 ul > li > * { color: black; }
91 .monospaced, code, pre {
92 font-family: "Courier New", Courier, monospace;
93 font-size: inherit;
94 color: navy;
95 padding: 0;
96 margin: 0;
98 pre {
99 white-space: pre-wrap;
102 #author {
103 color: #527bbd;
104 font-weight: bold;
105 font-size: 1.1em;
107 #email {
109 #revnumber, #revdate, #revremark {
112 #footer {
113 font-size: small;
114 border-top: 2px solid silver;
115 padding-top: 0.5em;
116 margin-top: 4.0em;
118 #footer-text {
119 float: left;
120 padding-bottom: 0.5em;
122 #footer-badges {
123 float: right;
124 padding-bottom: 0.5em;
127 #preamble {
128 margin-top: 1.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 {
134 margin-top: 1.0em;
135 margin-bottom: 1.5em;
137 div.admonitionblock {
138 margin-top: 2.0em;
139 margin-bottom: 2.0em;
140 margin-right: 10%;
141 color: #606060;
144 div.content { /* Block element content. */
145 padding: 0;
148 /* Block element titles. */
149 div.title, caption.title {
150 color: #527bbd;
151 font-weight: bold;
152 text-align: left;
153 margin-top: 1.0em;
154 margin-bottom: 0.5em;
156 div.title + * {
157 margin-top: 0;
160 td div.title:first-child {
161 margin-top: 0.0em;
163 div.content div.title:first-child {
164 margin-top: 0.0em;
166 div.content + div.title {
167 margin-top: 0.0em;
170 div.sidebarblock > div.content {
171 background: #ffffee;
172 border: 1px solid #dddddd;
173 border-left: 4px solid #f0f0f0;
174 padding: 0.5em;
177 div.listingblock > div.content {
178 border: 1px solid #dddddd;
179 border-left: 5px solid #f0f0f0;
180 background: #f8f8f8;
181 padding: 0.5em;
184 div.quoteblock, div.verseblock {
185 padding-left: 1.0em;
186 margin-left: 1.0em;
187 margin-right: 10%;
188 border-left: 5px solid #f0f0f0;
189 color: #888;
192 div.quoteblock > div.attribution {
193 padding-top: 0.5em;
194 text-align: right;
197 div.verseblock > pre.content {
198 font-family: inherit;
199 font-size: inherit;
201 div.verseblock > div.attribution {
202 padding-top: 0.75em;
203 text-align: left;
205 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
206 div.verseblock + div.attribution {
207 text-align: left;
210 div.admonitionblock .icon {
211 vertical-align: top;
212 font-size: 1.1em;
213 font-weight: bold;
214 text-decoration: underline;
215 color: #527bbd;
216 padding-right: 0.5em;
218 div.admonitionblock td.content {
219 padding-left: 0.5em;
220 border-left: 3px solid #dddddd;
223 div.exampleblock > div.content {
224 border-left: 3px solid #dddddd;
225 padding-left: 0.5em;
228 div.imageblock div.content { padding-left: 0; }
229 span.image img { border-style: none; vertical-align: text-bottom; }
230 a.image:visited { color: white; }
232 dl {
233 margin-top: 0.8em;
234 margin-bottom: 0.8em;
236 dt {
237 margin-top: 0.5em;
238 margin-bottom: 0;
239 font-style: normal;
240 color: navy;
242 dd > *:first-child {
243 margin-top: 0.1em;
246 ul, ol {
247 list-style-position: outside;
249 ol.arabic {
250 list-style-type: decimal;
252 ol.loweralpha {
253 list-style-type: lower-alpha;
255 ol.upperalpha {
256 list-style-type: upper-alpha;
258 ol.lowerroman {
259 list-style-type: lower-roman;
261 ol.upperroman {
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 {
268 margin-top: 0.1em;
269 margin-bottom: 0.1em;
272 tfoot {
273 font-weight: bold;
275 td > div.verse {
276 white-space: pre;
279 div.hdlist {
280 margin-top: 0.8em;
281 margin-bottom: 0.8em;
283 div.hdlist tr {
284 padding-bottom: 15px;
286 dt.hdlist1.strong, td.hdlist1.strong {
287 font-weight: bold;
289 td.hdlist1 {
290 vertical-align: top;
291 font-style: normal;
292 padding-right: 0.8em;
293 color: navy;
295 td.hdlist2 {
296 vertical-align: top;
298 div.hdlist.compact tr {
299 margin: 0;
300 padding-bottom: 0;
303 .comment {
304 background: yellow;
307 .footnote, .footnoteref {
308 font-size: 0.8em;
311 span.footnote, span.footnoteref {
312 vertical-align: super;
315 #footnotes {
316 margin: 20px 0 20px 0;
317 padding: 7px 0 0 0;
320 #footnotes div.footnote {
321 margin: 0 0 5px 0;
324 #footnotes hr {
325 border: none;
326 border-top: 1px solid silver;
327 height: 1px;
328 text-align: left;
329 margin-left: 0;
330 width: 20%;
331 min-width: 100px;
334 div.colist td {
335 padding-right: 0.5em;
336 padding-bottom: 0.3em;
337 vertical-align: top;
339 div.colist td img {
340 margin-top: 0.3em;
343 @media print {
344 #footer-badges { display: none; }
347 #toc {
348 margin-bottom: 2.5em;
351 #toctitle {
352 color: #527bbd;
353 font-size: 1.1em;
354 font-weight: bold;
355 margin-top: 1.0em;
356 margin-bottom: 0.1em;
359 div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
360 margin-top: 0;
361 margin-bottom: 0;
363 div.toclevel2 {
364 margin-left: 2em;
365 font-size: 0.9em;
367 div.toclevel3 {
368 margin-left: 4em;
369 font-size: 0.9em;
371 div.toclevel4 {
372 margin-left: 6em;
373 font-size: 0.9em;
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; }
421 * xhtml11 specific
423 * */
425 div.tableblock {
426 margin-top: 1.0em;
427 margin-bottom: 1.5em;
429 div.tableblock > table {
430 border: 3px solid #527bbd;
432 thead, p.table.header {
433 font-weight: bold;
434 color: #527bbd;
436 p.table {
437 margin-top: 0;
439 /* Because the table frame attribute is overridden by CSS in most browsers. */
440 div.tableblock > table[frame="void"] {
441 border-style: none;
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;
454 * html5 specific
456 * */
458 table.tableblock {
459 margin-top: 1.0em;
460 margin-bottom: 1.5em;
462 thead, p.tableblock.header {
463 font-weight: bold;
464 color: #527bbd;
466 p.tableblock {
467 margin-top: 0;
469 table.tableblock {
470 border-width: 3px;
471 border-spacing: 0px;
472 border-style: solid;
473 border-color: #527bbd;
474 border-collapse: collapse;
476 th.tableblock, td.tableblock {
477 border-width: 1px;
478 padding: 4px;
479 border-style: solid;
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 {
496 text-align: left;
498 th.tableblock.halign-center, td.tableblock.halign-center {
499 text-align: center;
501 th.tableblock.halign-right, td.tableblock.halign-right {
502 text-align: right;
505 th.tableblock.valign-top, td.tableblock.valign-top {
506 vertical-align: 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;
517 * manpage specific
519 * */
521 body.manpage h1 {
522 padding-top: 0.5em;
523 padding-bottom: 0.5em;
524 border-top: 2px solid silver;
525 border-bottom: 2px solid silver;
527 body.manpage h2 {
528 border-style: none;
530 body.manpage div.sectionbody {
531 margin-left: 3em;
534 @media print {
535 body.manpage div#toc { display: none; }
539 </style>
540 <script type="text/javascript">
541 /*<![CDATA[*/
542 var asciidoc = { // Namespace.
544 /////////////////////////////////////////////////////////////////////
545 // Table Of Contents generator
546 /////////////////////////////////////////////////////////////////////
548 /* Author: Mihai Bazon, September 2002
549 * http://students.infoiasi.ro/~mishoo
551 * Table Of Content generator
552 * Version: 0.4
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 */
561 // toclevels = 1..4.
562 toc: function (toclevels) {
564 function getText(el) {
565 var text = "";
566 for (var i = el.firstChild; i != null; i = i.nextSibling) {
567 if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
568 text += i.data;
569 else if (i.firstChild != null)
570 text += getText(i);
572 return text;
575 function TocEntry(el, text, toclevel) {
576 this.element = el;
577 this.text = text;
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
586 // browsers).
587 var iterate = function (el) {
588 for (var i = el.firstChild; i != null; i = i.nextSibling) {
589 if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
590 var mo = re.exec(i.tagName);
591 if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
592 result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
594 iterate(i);
598 iterate(el);
599 return result;
602 var toc = document.getElementById("toc");
603 if (!toc) {
604 return;
607 // Delete existing TOC entries in case we're reloading the TOC.
608 var tocEntriesToRemove = [];
609 var i;
610 for (i = 0; i < toc.childNodes.length; i++) {
611 var entry = toc.childNodes[i];
612 if (entry.nodeName.toLowerCase() == 'div'
613 && entry.getAttribute("class")
614 && entry.getAttribute("class").match(/^toclevel/))
615 tocEntriesToRemove.push(entry);
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");
631 div.appendChild(a);
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.
650 var i;
651 var noteholder = document.getElementById("footnotes");
652 if (!noteholder) {
653 return;
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");
668 var refs = {};
669 var n = 0;
670 for (i=0; i<spans.length; i++) {
671 if (spans[i].className == "footnote") {
672 n++;
673 var note = spans[i].getAttribute("data-note");
674 if (!note) {
675 // Use [\s\S] in place of . so multi-line matches work.
676 // Because JavaScript has no s (dotall) regex flag.
677 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
678 spans[i].innerHTML =
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;
691 if (n == 0)
692 noteholder.parentNode.removeChild(noteholder);
693 else {
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.
699 n = refs[href];
700 spans[i].innerHTML =
701 "[<a href='#_footnote_" + n +
702 "' title='View footnote' class='footnote'>" + n + "</a>]";
708 install: function(toclevels) {
709 var timerId;
711 function reinstall() {
712 asciidoc.footnotes();
713 if (toclevels) {
714 asciidoc.toc(toclevels);
718 function reinstallAndRemoveTimer() {
719 clearInterval(timerId);
720 reinstall();
723 timerId = setInterval(reinstall, 500);
724 if (document.addEventListener)
725 document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
726 else
727 window.onload = reinstallAndRemoveTimer;
731 asciidoc.install();
732 /*]]>*/
733 </script>
734 </head>
735 <body class="manpage">
736 <div id="header">
737 <h1>
738 git-cat-file(1) Manual Page
739 </h1>
740 <h2>NAME</h2>
741 <div class="sectionbody">
742 <p>git-cat-file -
743 Provide content or type and size information for repository objects
744 </p>
745 </div>
746 </div>
747 <div id="content">
748 <div class="sect1">
749 <h2 id="_synopsis">SYNOPSIS</h2>
750 <div class="sectionbody">
751 <div class="verseblock">
752 <pre class="content"><em>git cat-file</em> &lt;type&gt; &lt;object&gt;
753 <em>git cat-file</em> (-e | -p) &lt;object&gt;
754 <em>git cat-file</em> (-t | -s) [--allow-unknown-type] &lt;object&gt;
755 <em>git cat-file</em> (--batch | --batch-check | --batch-command) [--batch-all-objects]
756 [--buffer] [--follow-symlinks] [--unordered]
757 [--textconv | --filters] [-Z]
758 <em>git cat-file</em> (--textconv | --filters)
759 [&lt;rev&gt;:&lt;path|tree-ish&gt; | --path=&lt;path|tree-ish&gt; &lt;rev&gt;]</pre>
760 <div class="attribution">
761 </div></div>
762 </div>
763 </div>
764 <div class="sect1">
765 <h2 id="_description">DESCRIPTION</h2>
766 <div class="sectionbody">
767 <div class="paragraph"><p>In its first form, the command provides the content or the type of an object in
768 the repository. The type is required unless <code>-t</code> or <code>-p</code> is used to find the
769 object type, or <code>-s</code> is used to find the object size, or <code>--textconv</code> or
770 <code>--filters</code> is used (which imply type "blob").</p></div>
771 <div class="paragraph"><p>In the second form, a list of objects (separated by linefeeds) is provided on
772 stdin, and the SHA-1, type, and size of each object is printed on stdout. The
773 output format can be overridden using the optional <code>&lt;format&gt;</code> argument. If
774 either <code>--textconv</code> or <code>--filters</code> was specified, the input is expected to
775 list the object names followed by the path name, separated by a single
776 whitespace, so that the appropriate drivers can be determined.</p></div>
777 </div>
778 </div>
779 <div class="sect1">
780 <h2 id="_options">OPTIONS</h2>
781 <div class="sectionbody">
782 <div class="dlist"><dl>
783 <dt class="hdlist1">
784 &lt;object&gt;
785 </dt>
786 <dd>
788 The name of the object to show.
789 For a more complete list of ways to spell object names, see
790 the "SPECIFYING REVISIONS" section in <a href="gitrevisions.html">gitrevisions(7)</a>.
791 </p>
792 </dd>
793 <dt class="hdlist1">
795 </dt>
796 <dd>
798 Instead of the content, show the object type identified by
799 <code>&lt;object&gt;</code>.
800 </p>
801 </dd>
802 <dt class="hdlist1">
804 </dt>
805 <dd>
807 Instead of the content, show the object size identified by
808 <code>&lt;object&gt;</code>. If used with <code>--use-mailmap</code> option, will show
809 the size of updated object after replacing idents using the
810 mailmap mechanism.
811 </p>
812 </dd>
813 <dt class="hdlist1">
815 </dt>
816 <dd>
818 Exit with zero status if <code>&lt;object&gt;</code> exists and is a valid
819 object. If <code>&lt;object&gt;</code> is of an invalid format exit with non-zero and
820 emits an error on stderr.
821 </p>
822 </dd>
823 <dt class="hdlist1">
825 </dt>
826 <dd>
828 Pretty-print the contents of <code>&lt;object&gt;</code> based on its type.
829 </p>
830 </dd>
831 <dt class="hdlist1">
832 &lt;type&gt;
833 </dt>
834 <dd>
836 Typically this matches the real type of <code>&lt;object&gt;</code> but asking
837 for a type that can trivially be dereferenced from the given
838 <code>&lt;object&gt;</code> is also permitted. An example is to ask for a
839 "tree" with <code>&lt;object&gt;</code> being a commit object that contains it,
840 or to ask for a "blob" with <code>&lt;object&gt;</code> being a tag object that
841 points at it.
842 </p>
843 </dd>
844 <dt class="hdlist1">
845 --[no-]mailmap
846 </dt>
847 <dt class="hdlist1">
848 --[no-]use-mailmap
849 </dt>
850 <dd>
852 Use mailmap file to map author, committer and tagger names
853 and email addresses to canonical real names and email addresses.
854 See <a href="git-shortlog.html">git-shortlog(1)</a>.
855 </p>
856 </dd>
857 <dt class="hdlist1">
858 --textconv
859 </dt>
860 <dd>
862 Show the content as transformed by a textconv filter. In this case,
863 <code>&lt;object&gt;</code> has to be of the form <code>&lt;tree-ish&gt;:&lt;path&gt;</code>, or <code>:&lt;path&gt;</code> in
864 order to apply the filter to the content recorded in the index at
865 <code>&lt;path&gt;</code>.
866 </p>
867 </dd>
868 <dt class="hdlist1">
869 --filters
870 </dt>
871 <dd>
873 Show the content as converted by the filters configured in
874 the current working tree for the given <code>&lt;path&gt;</code> (i.e. smudge filters,
875 end-of-line conversion, etc). In this case, <code>&lt;object&gt;</code> has to be of
876 the form <code>&lt;tree-ish&gt;:&lt;path&gt;</code>, or <code>:&lt;path&gt;</code>.
877 </p>
878 </dd>
879 <dt class="hdlist1">
880 --path=&lt;path&gt;
881 </dt>
882 <dd>
884 For use with <code>--textconv</code> or <code>--filters</code>, to allow specifying an object
885 name and a path separately, e.g. when it is difficult to figure out
886 the revision from which the blob came.
887 </p>
888 </dd>
889 <dt class="hdlist1">
890 --batch
891 </dt>
892 <dt class="hdlist1">
893 --batch=&lt;format&gt;
894 </dt>
895 <dd>
897 Print object information and contents for each object provided
898 on stdin. May not be combined with any other options or arguments
899 except <code>--textconv</code>, <code>--filters</code>, or <code>--use-mailmap</code>.
900 </p>
901 <div class="openblock">
902 <div class="content">
903 <div class="ulist"><ul>
904 <li>
906 When used with <code>--textconv</code> or <code>--filters</code>, the input lines
907 must specify the path, separated by whitespace. See the section
908 <code>BATCH OUTPUT</code> below for details.
909 </p>
910 </li>
911 <li>
913 When used with <code>--use-mailmap</code>, for commit and tag objects, the
914 contents part of the output shows the identities replaced using the
915 mailmap mechanism, while the information part of the output shows
916 the size of the object as if it actually recorded the replacement
917 identities.
918 </p>
919 </li>
920 </ul></div>
921 </div></div>
922 </dd>
923 <dt class="hdlist1">
924 --batch-check
925 </dt>
926 <dt class="hdlist1">
927 --batch-check=&lt;format&gt;
928 </dt>
929 <dd>
931 Print object information for each object provided on stdin. May not be
932 combined with any other options or arguments except <code>--textconv</code>, <code>--filters</code>
933 or <code>--use-mailmap</code>.
934 </p>
935 <div class="openblock">
936 <div class="content">
937 <div class="ulist"><ul>
938 <li>
940 When used with <code>--textconv</code> or <code>--filters</code>, the input lines must
941 specify the path, separated by whitespace. See the section
942 <code>BATCH OUTPUT</code> below for details.
943 </p>
944 </li>
945 <li>
947 When used with <code>--use-mailmap</code>, for commit and tag objects, the
948 printed object information shows the size of the object as if the
949 identities recorded in it were replaced by the mailmap mechanism.
950 </p>
951 </li>
952 </ul></div>
953 </div></div>
954 </dd>
955 <dt class="hdlist1">
956 --batch-command
957 </dt>
958 <dt class="hdlist1">
959 --batch-command=&lt;format&gt;
960 </dt>
961 <dd>
963 Enter a command mode that reads commands and arguments from stdin. May
964 only be combined with <code>--buffer</code>, <code>--textconv</code>, <code>--use-mailmap</code> or
965 <code>--filters</code>.
966 </p>
967 <div class="openblock">
968 <div class="content">
969 <div class="ulist"><ul>
970 <li>
972 When used with <code>--textconv</code> or <code>--filters</code>, the input lines must
973 specify the path, separated by whitespace. See the section
974 <code>BATCH OUTPUT</code> below for details.
975 </p>
976 </li>
977 <li>
979 When used with <code>--use-mailmap</code>, for commit and tag objects, the
980 <code>contents</code> command shows the identities replaced using the
981 mailmap mechanism, while the <code>info</code> command shows the size
982 of the object as if it actually recorded the replacement
983 identities.
984 </p>
985 </li>
986 </ul></div>
987 </div></div>
988 <div class="paragraph"><p><code>--batch-command</code> recognizes the following commands:</p></div>
989 <div class="openblock">
990 <div class="content">
991 <div class="dlist"><dl>
992 <dt class="hdlist1">
993 contents &lt;object&gt;
994 </dt>
995 <dd>
997 Print object contents for object reference <code>&lt;object&gt;</code>. This corresponds to
998 the output of <code>--batch</code>.
999 </p>
1000 </dd>
1001 <dt class="hdlist1">
1002 info &lt;object&gt;
1003 </dt>
1004 <dd>
1006 Print object info for object reference <code>&lt;object&gt;</code>. This corresponds to the
1007 output of <code>--batch-check</code>.
1008 </p>
1009 </dd>
1010 <dt class="hdlist1">
1011 flush
1012 </dt>
1013 <dd>
1015 Used with <code>--buffer</code> to execute all preceding commands that were issued
1016 since the beginning or since the last flush was issued. When <code>--buffer</code>
1017 is used, no output will come until a <code>flush</code> is issued. When <code>--buffer</code>
1018 is not used, commands are flushed each time without issuing <code>flush</code>.
1019 </p>
1020 </dd>
1021 </dl></div>
1022 </div></div>
1023 </dd>
1024 <dt class="hdlist1">
1025 --batch-all-objects
1026 </dt>
1027 <dd>
1029 Instead of reading a list of objects on stdin, perform the
1030 requested batch operation on all objects in the repository and
1031 any alternate object stores (not just reachable objects).
1032 Requires <code>--batch</code> or <code>--batch-check</code> be specified. By default,
1033 the objects are visited in order sorted by their hashes; see
1034 also <code>--unordered</code> below. Objects are presented as-is, without
1035 respecting the "replace" mechanism of <a href="git-replace.html">git-replace(1)</a>.
1036 </p>
1037 </dd>
1038 <dt class="hdlist1">
1039 --buffer
1040 </dt>
1041 <dd>
1043 Normally batch output is flushed after each object is output, so
1044 that a process can interactively read and write from
1045 <code>cat-file</code>. With this option, the output uses normal stdio
1046 buffering; this is much more efficient when invoking
1047 <code>--batch-check</code> or <code>--batch-command</code> on a large number of objects.
1048 </p>
1049 </dd>
1050 <dt class="hdlist1">
1051 --unordered
1052 </dt>
1053 <dd>
1055 When <code>--batch-all-objects</code> is in use, visit objects in an
1056 order which may be more efficient for accessing the object
1057 contents than hash order. The exact details of the order are
1058 unspecified, but if you do not require a specific order, this
1059 should generally result in faster output, especially with
1060 <code>--batch</code>. Note that <code>cat-file</code> will still show each object
1061 only once, even if it is stored multiple times in the
1062 repository.
1063 </p>
1064 </dd>
1065 <dt class="hdlist1">
1066 --allow-unknown-type
1067 </dt>
1068 <dd>
1070 Allow <code>-s</code> or <code>-t</code> to query broken/corrupt objects of unknown type.
1071 </p>
1072 </dd>
1073 <dt class="hdlist1">
1074 --follow-symlinks
1075 </dt>
1076 <dd>
1078 With <code>--batch</code> or <code>--batch-check</code>, follow symlinks inside the
1079 repository when requesting objects with extended SHA-1
1080 expressions of the form tree-ish:path-in-tree. Instead of
1081 providing output about the link itself, provide output about
1082 the linked-to object. If a symlink points outside the
1083 tree-ish (e.g. a link to <code>/foo</code> or a root-level link to <code>../foo</code>),
1084 the portion of the link which is outside the tree will be
1085 printed.
1086 </p>
1087 <div class="paragraph"><p>This option does not (currently) work correctly when an object in the
1088 index is specified (e.g. <code>:link</code> instead of <code>HEAD:link</code>) rather than
1089 one in the tree.</p></div>
1090 <div class="paragraph"><p>This option cannot (currently) be used unless <code>--batch</code> or
1091 <code>--batch-check</code> is used.</p></div>
1092 <div class="paragraph"><p>For example, consider a git repository containing:</p></div>
1093 <div class="openblock">
1094 <div class="content">
1095 <div class="literalblock">
1096 <div class="content">
1097 <pre><code>f: a file containing "hello\n"
1098 link: a symlink to f
1099 dir/link: a symlink to ../f
1100 plink: a symlink to ../f
1101 alink: a symlink to /etc/passwd</code></pre>
1102 </div></div>
1103 </div></div>
1104 <div class="paragraph"><p>For a regular file <code>f</code>, <code>echo HEAD:f | git cat-file --batch</code> would print</p></div>
1105 <div class="openblock">
1106 <div class="content">
1107 <div class="literalblock">
1108 <div class="content">
1109 <pre><code>ce013625030ba8dba906f756967f9e9ca394464a blob 6</code></pre>
1110 </div></div>
1111 </div></div>
1112 <div class="paragraph"><p>And <code>echo HEAD:link | git cat-file --batch --follow-symlinks</code> would
1113 print the same thing, as would <code>HEAD:dir/link</code>, as they both point at
1114 <code>HEAD:f</code>.</p></div>
1115 <div class="paragraph"><p>Without <code>--follow-symlinks</code>, these would print data about the symlink
1116 itself. In the case of <code>HEAD:link</code>, you would see</p></div>
1117 <div class="openblock">
1118 <div class="content">
1119 <div class="literalblock">
1120 <div class="content">
1121 <pre><code>4d1ae35ba2c8ec712fa2a379db44ad639ca277bd blob 1</code></pre>
1122 </div></div>
1123 </div></div>
1124 <div class="paragraph"><p>Both <code>plink</code> and <code>alink</code> point outside the tree, so they would
1125 respectively print:</p></div>
1126 <div class="openblock">
1127 <div class="content">
1128 <div class="literalblock">
1129 <div class="content">
1130 <pre><code>symlink 4
1131 ../f</code></pre>
1132 </div></div>
1133 <div class="literalblock">
1134 <div class="content">
1135 <pre><code>symlink 11
1136 /etc/passwd</code></pre>
1137 </div></div>
1138 </div></div>
1139 </dd>
1140 <dt class="hdlist1">
1142 </dt>
1143 <dd>
1145 Only meaningful with <code>--batch</code>, <code>--batch-check</code>, or
1146 <code>--batch-command</code>; input and output is NUL-delimited instead of
1147 newline-delimited.
1148 </p>
1149 </dd>
1150 <dt class="hdlist1">
1152 </dt>
1153 <dd>
1155 Only meaningful with <code>--batch</code>, <code>--batch-check</code>, or
1156 <code>--batch-command</code>; input is NUL-delimited instead of
1157 newline-delimited. This option is deprecated in favor of
1158 <code>-Z</code> as the output can otherwise be ambiguous.
1159 </p>
1160 </dd>
1161 </dl></div>
1162 </div>
1163 </div>
1164 <div class="sect1">
1165 <h2 id="_output">OUTPUT</h2>
1166 <div class="sectionbody">
1167 <div class="paragraph"><p>If <code>-t</code> is specified, one of the <code>&lt;type&gt;</code>.</p></div>
1168 <div class="paragraph"><p>If <code>-s</code> is specified, the size of the <code>&lt;object&gt;</code> in bytes.</p></div>
1169 <div class="paragraph"><p>If <code>-e</code> is specified, no output, unless the <code>&lt;object&gt;</code> is malformed.</p></div>
1170 <div class="paragraph"><p>If <code>-p</code> is specified, the contents of <code>&lt;object&gt;</code> are pretty-printed.</p></div>
1171 <div class="paragraph"><p>If <code>&lt;type&gt;</code> is specified, the raw (though uncompressed) contents of the <code>&lt;object&gt;</code>
1172 will be returned.</p></div>
1173 </div>
1174 </div>
1175 <div class="sect1">
1176 <h2 id="_batch_output">BATCH OUTPUT</h2>
1177 <div class="sectionbody">
1178 <div class="paragraph"><p>If <code>--batch</code> or <code>--batch-check</code> is given, <code>cat-file</code> will read objects
1179 from stdin, one per line, and print information about them. By default,
1180 the whole line is considered as an object, as if it were fed to
1181 <a href="git-rev-parse.html">git-rev-parse(1)</a>.</p></div>
1182 <div class="paragraph"><p>When <code>--batch-command</code> is given, <code>cat-file</code> will read commands from stdin,
1183 one per line, and print information based on the command given. With
1184 <code>--batch-command</code>, the <code>info</code> command followed by an object will print
1185 information about the object the same way <code>--batch-check</code> would, and the
1186 <code>contents</code> command followed by an object prints contents in the same way
1187 <code>--batch</code> would.</p></div>
1188 <div class="paragraph"><p>You can specify the information shown for each object by using a custom
1189 <code>&lt;format&gt;</code>. The <code>&lt;format&gt;</code> is copied literally to stdout for each
1190 object, with placeholders of the form <code>%(atom)</code> expanded, followed by a
1191 newline. The available atoms are:</p></div>
1192 <div class="dlist"><dl>
1193 <dt class="hdlist1">
1194 <code>objectname</code>
1195 </dt>
1196 <dd>
1198 The full hex representation of the object name.
1199 </p>
1200 </dd>
1201 <dt class="hdlist1">
1202 <code>objecttype</code>
1203 </dt>
1204 <dd>
1206 The type of the object (the same as <code>cat-file -t</code> reports).
1207 </p>
1208 </dd>
1209 <dt class="hdlist1">
1210 <code>objectsize</code>
1211 </dt>
1212 <dd>
1214 The size, in bytes, of the object (the same as <code>cat-file -s</code>
1215 reports).
1216 </p>
1217 </dd>
1218 <dt class="hdlist1">
1219 <code>objectsize:disk</code>
1220 </dt>
1221 <dd>
1223 The size, in bytes, that the object takes up on disk. See the
1224 note about on-disk sizes in the <code>CAVEATS</code> section below.
1225 </p>
1226 </dd>
1227 <dt class="hdlist1">
1228 <code>deltabase</code>
1229 </dt>
1230 <dd>
1232 If the object is stored as a delta on-disk, this expands to the
1233 full hex representation of the delta base object name.
1234 Otherwise, expands to the null OID (all zeroes). See <code>CAVEATS</code>
1235 below.
1236 </p>
1237 </dd>
1238 <dt class="hdlist1">
1239 <code>rest</code>
1240 </dt>
1241 <dd>
1243 If this atom is used in the output string, input lines are split
1244 at the first whitespace boundary. All characters before that
1245 whitespace are considered to be the object name; characters
1246 after that first run of whitespace (i.e., the "rest" of the
1247 line) are output in place of the <code>%(rest)</code> atom.
1248 </p>
1249 </dd>
1250 </dl></div>
1251 <div class="paragraph"><p>If no format is specified, the default format is <code>%(objectname)
1252 %(objecttype) %(objectsize)</code>.</p></div>
1253 <div class="paragraph"><p>If <code>--batch</code> is specified, or if <code>--batch-command</code> is used with the <code>contents</code>
1254 command, the object information is followed by the object contents (consisting
1255 of <code>%(objectsize)</code> bytes), followed by a newline.</p></div>
1256 <div class="paragraph"><p>For example, <code>--batch</code> without a custom format would produce:</p></div>
1257 <div class="listingblock">
1258 <div class="content">
1259 <pre><code>&lt;oid&gt; SP &lt;type&gt; SP &lt;size&gt; LF
1260 &lt;contents&gt; LF</code></pre>
1261 </div></div>
1262 <div class="paragraph"><p>Whereas <code>--batch-check='%(objectname) %(objecttype)'</code> would produce:</p></div>
1263 <div class="listingblock">
1264 <div class="content">
1265 <pre><code>&lt;oid&gt; SP &lt;type&gt; LF</code></pre>
1266 </div></div>
1267 <div class="paragraph"><p>If a name is specified on stdin that cannot be resolved to an object in
1268 the repository, then <code>cat-file</code> will ignore any custom format and print:</p></div>
1269 <div class="listingblock">
1270 <div class="content">
1271 <pre><code>&lt;object&gt; SP missing LF</code></pre>
1272 </div></div>
1273 <div class="paragraph"><p>If a name is specified that might refer to more than one object (an ambiguous short sha), then <code>cat-file</code> will ignore any custom format and print:</p></div>
1274 <div class="listingblock">
1275 <div class="content">
1276 <pre><code>&lt;object&gt; SP ambiguous LF</code></pre>
1277 </div></div>
1278 <div class="paragraph"><p>If <code>--follow-symlinks</code> is used, and a symlink in the repository points
1279 outside the repository, then <code>cat-file</code> will ignore any custom format
1280 and print:</p></div>
1281 <div class="listingblock">
1282 <div class="content">
1283 <pre><code>symlink SP &lt;size&gt; LF
1284 &lt;symlink&gt; LF</code></pre>
1285 </div></div>
1286 <div class="paragraph"><p>The symlink will either be absolute (beginning with a <code>/</code>), or relative
1287 to the tree root. For instance, if dir/link points to <code>../../foo</code>, then
1288 <code>&lt;symlink&gt;</code> will be <code>../foo</code>. <code>&lt;size&gt;</code> is the size of the symlink in bytes.</p></div>
1289 <div class="paragraph"><p>If <code>--follow-symlinks</code> is used, the following error messages will be
1290 displayed:</p></div>
1291 <div class="listingblock">
1292 <div class="content">
1293 <pre><code>&lt;object&gt; SP missing LF</code></pre>
1294 </div></div>
1295 <div class="paragraph"><p>is printed when the initial symlink requested does not exist.</p></div>
1296 <div class="listingblock">
1297 <div class="content">
1298 <pre><code>dangling SP &lt;size&gt; LF
1299 &lt;object&gt; LF</code></pre>
1300 </div></div>
1301 <div class="paragraph"><p>is printed when the initial symlink exists, but something that
1302 it (transitive-of) points to does not.</p></div>
1303 <div class="listingblock">
1304 <div class="content">
1305 <pre><code>loop SP &lt;size&gt; LF
1306 &lt;object&gt; LF</code></pre>
1307 </div></div>
1308 <div class="paragraph"><p>is printed for symlink loops (or any symlinks that
1309 require more than 40 link resolutions to resolve).</p></div>
1310 <div class="listingblock">
1311 <div class="content">
1312 <pre><code>notdir SP &lt;size&gt; LF
1313 &lt;object&gt; LF</code></pre>
1314 </div></div>
1315 <div class="paragraph"><p>is printed when, during symlink resolution, a file is used as a
1316 directory name.</p></div>
1317 <div class="paragraph"><p>Alternatively, when <code>-Z</code> is passed, the line feeds in any of the above examples
1318 are replaced with NUL terminators. This ensures that output will be parsable if
1319 the output itself would contain a linefeed and is thus recommended for
1320 scripting purposes.</p></div>
1321 </div>
1322 </div>
1323 <div class="sect1">
1324 <h2 id="_caveats">CAVEATS</h2>
1325 <div class="sectionbody">
1326 <div class="paragraph"><p>Note that the sizes of objects on disk are reported accurately, but care
1327 should be taken in drawing conclusions about which refs or objects are
1328 responsible for disk usage. The size of a packed non-delta object may be
1329 much larger than the size of objects which delta against it, but the
1330 choice of which object is the base and which is the delta is arbitrary
1331 and is subject to change during a repack.</p></div>
1332 <div class="paragraph"><p>Note also that multiple copies of an object may be present in the object
1333 database; in this case, it is undefined which copy&#8217;s size or delta base
1334 will be reported.</p></div>
1335 </div>
1336 </div>
1337 <div class="sect1">
1338 <h2 id="_git">GIT</h2>
1339 <div class="sectionbody">
1340 <div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
1341 </div>
1342 </div>
1343 </div>
1344 <div id="footnotes"><hr /></div>
1345 <div id="footer">
1346 <div id="footer-text">
1347 Last updated
1348 2023-06-23 13:24:09 PDT
1349 </div>
1350 </div>
1351 </body>
1352 </html>