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-cat-file(
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-cat-file(
1) Manual Page
741 <div class=
"sectionbody">
743 Provide contents or details of repository objects
749 <h2 id=
"_synopsis">SYNOPSIS
</h2>
750 <div class=
"sectionbody">
751 <div class=
"verseblock">
752 <pre class=
"content"><em>git cat-file
</em> <type
> <object
>
753 <em>git cat-file
</em> (-e | -p)
<object
>
754 <em>git cat-file
</em> (-t | -s) [--allow-unknown-type]
<object
>
755 <em>git cat-file
</em> (--textconv | --filters)
756 [
<rev
>:
<path|tree-ish
> | --path=
<path|tree-ish
> <rev
>]
757 <em>git cat-file
</em> (--batch | --batch-check | --batch-command) [--batch-all-objects]
758 [--buffer] [--follow-symlinks] [--unordered]
759 [--textconv | --filters] [-Z]
</pre>
760 <div class=
"attribution">
765 <h2 id=
"_description">DESCRIPTION
</h2>
766 <div class=
"sectionbody">
767 <div class=
"paragraph"><p>Output the contents or other properties such as size, type or delta
768 information of one or more objects.
</p></div>
769 <div class=
"paragraph"><p>This command can operate in two modes, depending on whether an option
770 from the
<code>--batch
</code> family is specified.
</p></div>
771 <div class=
"paragraph"><p>In non-batch mode, the command provides information on an object
772 named on the command line.
</p></div>
773 <div class=
"paragraph"><p>In batch mode, arguments are read from standard input.
</p></div>
777 <h2 id=
"_options">OPTIONS
</h2>
778 <div class=
"sectionbody">
779 <div class=
"dlist"><dl>
785 The name of the object to show.
786 For a more complete list of ways to spell object names, see
787 the
"SPECIFYING REVISIONS" section in
<a href=
"gitrevisions.html">gitrevisions(
7)
</a>.
795 Instead of the content, show the object type identified by
796 <code><object
></code>.
804 Instead of the content, show the object size identified by
805 <code><object
></code>. If used with
<code>--use-mailmap
</code> option, will show
806 the size of updated object after replacing idents using the
815 Exit with zero status if
<code><object
></code> exists and is a valid
816 object. If
<code><object
></code> is of an invalid format, exit with non-zero
817 status and emit an error on stderr.
825 Pretty-print the contents of
<code><object
></code> based on its type.
833 Typically this matches the real type of
<code><object
></code> but asking
834 for a type that can trivially be dereferenced from the given
835 <code><object
></code> is also permitted. An example is to ask for a
836 "tree" with
<code><object
></code> being a commit object that contains it,
837 or to ask for a
"blob" with
<code><object
></code> being a tag object that
849 Use mailmap file to map author, committer and tagger names
850 and email addresses to canonical real names and email addresses.
851 See
<a href=
"git-shortlog.html">git-shortlog(
1)
</a>.
859 Show the content as transformed by a textconv filter. In this case,
860 <code><object
></code> has to be of the form
<code><tree-ish
>:
<path
></code>, or
<code>:
<path
></code> in
861 order to apply the filter to the content recorded in the index at
862 <code><path
></code>.
870 Show the content as converted by the filters configured in
871 the current working tree for the given
<code><path
></code> (i.e. smudge filters,
872 end-of-line conversion, etc). In this case,
<code><object
></code> has to be of
873 the form
<code><tree-ish
>:
<path
></code>, or
<code>:
<path
></code>.
881 For use with
<code>--textconv
</code> or
<code>--filters
</code>, to allow specifying an object
882 name and a path separately, e.g. when it is difficult to figure out
883 the revision from which the blob came.
890 --batch=
<format
>
894 Print object information and contents for each object provided
895 on stdin. May not be combined with any other options or arguments
896 except
<code>--textconv
</code>,
<code>--filters
</code>, or
<code>--use-mailmap
</code>.
898 <div class=
"openblock">
899 <div class=
"content">
900 <div class=
"ulist"><ul>
903 When used with
<code>--textconv
</code> or
<code>--filters
</code>, the input lines
904 must specify the path, separated by whitespace. See the section
905 <code>BATCH OUTPUT
</code> below for details.
910 When used with
<code>--use-mailmap
</code>, for commit and tag objects, the
911 contents part of the output shows the identities replaced using the
912 mailmap mechanism, while the information part of the output shows
913 the size of the object as if it actually recorded the replacement
924 --batch-check=
<format
>
928 Print object information for each object provided on stdin. May not be
929 combined with any other options or arguments except
<code>--textconv
</code>,
<code>--filters
</code>
930 or
<code>--use-mailmap
</code>.
932 <div class=
"openblock">
933 <div class=
"content">
934 <div class=
"ulist"><ul>
937 When used with
<code>--textconv
</code> or
<code>--filters
</code>, the input lines must
938 specify the path, separated by whitespace. See the section
939 <code>BATCH OUTPUT
</code> below for details.
944 When used with
<code>--use-mailmap
</code>, for commit and tag objects, the
945 printed object information shows the size of the object as if the
946 identities recorded in it were replaced by the mailmap mechanism.
956 --batch-command=
<format
>
960 Enter a command mode that reads commands and arguments from stdin. May
961 only be combined with
<code>--buffer
</code>,
<code>--textconv
</code>,
<code>--use-mailmap
</code> or
962 <code>--filters
</code>.
964 <div class=
"openblock">
965 <div class=
"content">
966 <div class=
"ulist"><ul>
969 When used with
<code>--textconv
</code> or
<code>--filters
</code>, the input lines must
970 specify the path, separated by whitespace. See the section
971 <code>BATCH OUTPUT
</code> below for details.
976 When used with
<code>--use-mailmap
</code>, for commit and tag objects, the
977 <code>contents
</code> command shows the identities replaced using the
978 mailmap mechanism, while the
<code>info
</code> command shows the size
979 of the object as if it actually recorded the replacement
985 <div class=
"paragraph"><p><code>--batch-command
</code> recognizes the following commands:
</p></div>
986 <div class=
"openblock">
987 <div class=
"content">
988 <div class=
"dlist"><dl>
990 contents
<object
>
994 Print object contents for object reference
<code><object
></code>. This corresponds to
995 the output of
<code>--batch
</code>.
1003 Print object info for object reference
<code><object
></code>. This corresponds to the
1004 output of
<code>--batch-check
</code>.
1007 <dt class=
"hdlist1">
1012 Used with
<code>--buffer
</code> to execute all preceding commands that were issued
1013 since the beginning or since the last flush was issued. When
<code>--buffer
</code>
1014 is used, no output will come until a
<code>flush
</code> is issued. When
<code>--buffer
</code>
1015 is not used, commands are flushed each time without issuing
<code>flush
</code>.
1021 <dt class=
"hdlist1">
1026 Instead of reading a list of objects on stdin, perform the
1027 requested batch operation on all objects in the repository and
1028 any alternate object stores (not just reachable objects).
1029 Requires
<code>--batch
</code> or
<code>--batch-check
</code> be specified. By default,
1030 the objects are visited in order sorted by their hashes; see
1031 also
<code>--unordered
</code> below. Objects are presented as-is, without
1032 respecting the
"replace" mechanism of
<a href=
"git-replace.html">git-replace(
1)
</a>.
1035 <dt class=
"hdlist1">
1040 Normally batch output is flushed after each object is output, so
1041 that a process can interactively read and write from
1042 <code>cat-file
</code>. With this option, the output uses normal stdio
1043 buffering; this is much more efficient when invoking
1044 <code>--batch-check
</code> or
<code>--batch-command
</code> on a large number of objects.
1047 <dt class=
"hdlist1">
1052 When
<code>--batch-all-objects
</code> is in use, visit objects in an
1053 order which may be more efficient for accessing the object
1054 contents than hash order. The exact details of the order are
1055 unspecified, but if you do not require a specific order, this
1056 should generally result in faster output, especially with
1057 <code>--batch
</code>. Note that
<code>cat-file
</code> will still show each object
1058 only once, even if it is stored multiple times in the
1062 <dt class=
"hdlist1">
1063 --allow-unknown-type
1067 Allow
<code>-s
</code> or
<code>-t
</code> to query broken/corrupt objects of unknown type.
1070 <dt class=
"hdlist1">
1075 With
<code>--batch
</code> or
<code>--batch-check
</code>, follow symlinks inside the
1076 repository when requesting objects with extended SHA-
1
1077 expressions of the form tree-ish:path-in-tree. Instead of
1078 providing output about the link itself, provide output about
1079 the linked-to object. If a symlink points outside the
1080 tree-ish (e.g. a link to
<code>/foo
</code> or a root-level link to
<code>../foo
</code>),
1081 the portion of the link which is outside the tree will be
1084 <div class=
"paragraph"><p>This option does not (currently) work correctly when an object in the
1085 index is specified (e.g.
<code>:link
</code> instead of
<code>HEAD:link
</code>) rather than
1086 one in the tree.
</p></div>
1087 <div class=
"paragraph"><p>This option cannot (currently) be used unless
<code>--batch
</code> or
1088 <code>--batch-check
</code> is used.
</p></div>
1089 <div class=
"paragraph"><p>For example, consider a git repository containing:
</p></div>
1090 <div class=
"openblock">
1091 <div class=
"content">
1092 <div class=
"literalblock">
1093 <div class=
"content">
1094 <pre><code>f: a file containing
"hello\n"
1095 link: a symlink to f
1096 dir/link: a symlink to ../f
1097 plink: a symlink to ../f
1098 alink: a symlink to /etc/passwd
</code></pre>
1101 <div class=
"paragraph"><p>For a regular file
<code>f
</code>,
<code>echo HEAD:f | git cat-file --batch
</code> would print
</p></div>
1102 <div class=
"openblock">
1103 <div class=
"content">
1104 <div class=
"literalblock">
1105 <div class=
"content">
1106 <pre><code>ce013625030ba8dba906f756967f9e9ca394464a blob
6</code></pre>
1109 <div class=
"paragraph"><p>And
<code>echo HEAD:link | git cat-file --batch --follow-symlinks
</code> would
1110 print the same thing, as would
<code>HEAD:dir/link
</code>, as they both point at
1111 <code>HEAD:f
</code>.
</p></div>
1112 <div class=
"paragraph"><p>Without
<code>--follow-symlinks
</code>, these would print data about the symlink
1113 itself. In the case of
<code>HEAD:link
</code>, you would see
</p></div>
1114 <div class=
"openblock">
1115 <div class=
"content">
1116 <div class=
"literalblock">
1117 <div class=
"content">
1118 <pre><code>4d1ae35ba2c8ec712fa2a379db44ad639ca277bd blob
1</code></pre>
1121 <div class=
"paragraph"><p>Both
<code>plink
</code> and
<code>alink
</code> point outside the tree, so they would
1122 respectively print:
</p></div>
1123 <div class=
"openblock">
1124 <div class=
"content">
1125 <div class=
"literalblock">
1126 <div class=
"content">
1127 <pre><code>symlink
4
1130 <div class=
"literalblock">
1131 <div class=
"content">
1132 <pre><code>symlink
11
1133 /etc/passwd
</code></pre>
1137 <dt class=
"hdlist1">
1142 Only meaningful with
<code>--batch
</code>,
<code>--batch-check
</code>, or
1143 <code>--batch-command
</code>; input and output is NUL-delimited instead of
1147 <dt class=
"hdlist1">
1152 Only meaningful with
<code>--batch
</code>,
<code>--batch-check
</code>, or
1153 <code>--batch-command
</code>; input is NUL-delimited instead of
1154 newline-delimited. This option is deprecated in favor of
1155 <code>-Z
</code> as the output can otherwise be ambiguous.
1162 <h2 id=
"_output">OUTPUT
</h2>
1163 <div class=
"sectionbody">
1164 <div class=
"paragraph"><p>If
<code>-t
</code> is specified, one of the
<code><type
></code>.
</p></div>
1165 <div class=
"paragraph"><p>If
<code>-s
</code> is specified, the size of the
<code><object
></code> in bytes.
</p></div>
1166 <div class=
"paragraph"><p>If
<code>-e
</code> is specified, no output, unless the
<code><object
></code> is malformed.
</p></div>
1167 <div class=
"paragraph"><p>If
<code>-p
</code> is specified, the contents of
<code><object
></code> are pretty-printed.
</p></div>
1168 <div class=
"paragraph"><p>If
<code><type
></code> is specified, the raw (though uncompressed) contents of the
<code><object
></code>
1169 will be returned.
</p></div>
1173 <h2 id=
"_batch_output">BATCH OUTPUT
</h2>
1174 <div class=
"sectionbody">
1175 <div class=
"paragraph"><p>If
<code>--batch
</code> or
<code>--batch-check
</code> is given,
<code>cat-file
</code> will read objects
1176 from stdin, one per line, and print information about them. By default,
1177 the whole line is considered as an object, as if it were fed to
1178 <a href=
"git-rev-parse.html">git-rev-parse(
1)
</a>.
</p></div>
1179 <div class=
"paragraph"><p>When
<code>--batch-command
</code> is given,
<code>cat-file
</code> will read commands from stdin,
1180 one per line, and print information based on the command given. With
1181 <code>--batch-command
</code>, the
<code>info
</code> command followed by an object will print
1182 information about the object the same way
<code>--batch-check
</code> would, and the
1183 <code>contents
</code> command followed by an object prints contents in the same way
1184 <code>--batch
</code> would.
</p></div>
1185 <div class=
"paragraph"><p>You can specify the information shown for each object by using a custom
1186 <code><format
></code>. The
<code><format
></code> is copied literally to stdout for each
1187 object, with placeholders of the form
<code>%(atom)
</code> expanded, followed by a
1188 newline. The available atoms are:
</p></div>
1189 <div class=
"dlist"><dl>
1190 <dt class=
"hdlist1">
1191 <code>objectname
</code>
1195 The full hex representation of the object name.
1198 <dt class=
"hdlist1">
1199 <code>objecttype
</code>
1203 The type of the object (the same as
<code>cat-file -t
</code> reports).
1206 <dt class=
"hdlist1">
1207 <code>objectsize
</code>
1211 The size, in bytes, of the object (the same as
<code>cat-file -s
</code>
1215 <dt class=
"hdlist1">
1216 <code>objectsize:disk
</code>
1220 The size, in bytes, that the object takes up on disk. See the
1221 note about on-disk sizes in the
<code>CAVEATS
</code> section below.
1224 <dt class=
"hdlist1">
1225 <code>deltabase
</code>
1229 If the object is stored as a delta on-disk, this expands to the
1230 full hex representation of the delta base object name.
1231 Otherwise, expands to the null OID (all zeroes). See
<code>CAVEATS
</code>
1235 <dt class=
"hdlist1">
1240 If this atom is used in the output string, input lines are split
1241 at the first whitespace boundary. All characters before that
1242 whitespace are considered to be the object name; characters
1243 after that first run of whitespace (i.e., the
"rest" of the
1244 line) are output in place of the
<code>%(rest)
</code> atom.
1248 <div class=
"paragraph"><p>If no format is specified, the default format is
<code>%(objectname)
1249 %(objecttype) %(objectsize)
</code>.
</p></div>
1250 <div class=
"paragraph"><p>If
<code>--batch
</code> is specified, or if
<code>--batch-command
</code> is used with the
<code>contents
</code>
1251 command, the object information is followed by the object contents (consisting
1252 of
<code>%(objectsize)
</code> bytes), followed by a newline.
</p></div>
1253 <div class=
"paragraph"><p>For example,
<code>--batch
</code> without a custom format would produce:
</p></div>
1254 <div class=
"listingblock">
1255 <div class=
"content">
1256 <pre><code><oid
> SP
<type
> SP
<size
> LF
1257 <contents
> LF
</code></pre>
1259 <div class=
"paragraph"><p>Whereas
<code>--batch-check='%(objectname) %(objecttype)'
</code> would produce:
</p></div>
1260 <div class=
"listingblock">
1261 <div class=
"content">
1262 <pre><code><oid
> SP
<type
> LF
</code></pre>
1264 <div class=
"paragraph"><p>If a name is specified on stdin that cannot be resolved to an object in
1265 the repository, then
<code>cat-file
</code> will ignore any custom format and print:
</p></div>
1266 <div class=
"listingblock">
1267 <div class=
"content">
1268 <pre><code><object
> SP missing LF
</code></pre>
1270 <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>
1271 <div class=
"listingblock">
1272 <div class=
"content">
1273 <pre><code><object
> SP ambiguous LF
</code></pre>
1275 <div class=
"paragraph"><p>If
<code>--follow-symlinks
</code> is used, and a symlink in the repository points
1276 outside the repository, then
<code>cat-file
</code> will ignore any custom format
1277 and print:
</p></div>
1278 <div class=
"listingblock">
1279 <div class=
"content">
1280 <pre><code>symlink SP
<size
> LF
1281 <symlink
> LF
</code></pre>
1283 <div class=
"paragraph"><p>The symlink will either be absolute (beginning with a
<code>/
</code>), or relative
1284 to the tree root. For instance, if dir/link points to
<code>../../foo
</code>, then
1285 <code><symlink
></code> will be
<code>../foo
</code>.
<code><size
></code> is the size of the symlink in bytes.
</p></div>
1286 <div class=
"paragraph"><p>If
<code>--follow-symlinks
</code> is used, the following error messages will be
1287 displayed:
</p></div>
1288 <div class=
"listingblock">
1289 <div class=
"content">
1290 <pre><code><object
> SP missing LF
</code></pre>
1292 <div class=
"paragraph"><p>is printed when the initial symlink requested does not exist.
</p></div>
1293 <div class=
"listingblock">
1294 <div class=
"content">
1295 <pre><code>dangling SP
<size
> LF
1296 <object
> LF
</code></pre>
1298 <div class=
"paragraph"><p>is printed when the initial symlink exists, but something that
1299 it (transitive-of) points to does not.
</p></div>
1300 <div class=
"listingblock">
1301 <div class=
"content">
1302 <pre><code>loop SP
<size
> LF
1303 <object
> LF
</code></pre>
1305 <div class=
"paragraph"><p>is printed for symlink loops (or any symlinks that
1306 require more than
40 link resolutions to resolve).
</p></div>
1307 <div class=
"listingblock">
1308 <div class=
"content">
1309 <pre><code>notdir SP
<size
> LF
1310 <object
> LF
</code></pre>
1312 <div class=
"paragraph"><p>is printed when, during symlink resolution, a file is used as a
1313 directory name.
</p></div>
1314 <div class=
"paragraph"><p>Alternatively, when
<code>-Z
</code> is passed, the line feeds in any of the above examples
1315 are replaced with NUL terminators. This ensures that output will be parsable if
1316 the output itself would contain a linefeed and is thus recommended for
1317 scripting purposes.
</p></div>
1321 <h2 id=
"_caveats">CAVEATS
</h2>
1322 <div class=
"sectionbody">
1323 <div class=
"paragraph"><p>Note that the sizes of objects on disk are reported accurately, but care
1324 should be taken in drawing conclusions about which refs or objects are
1325 responsible for disk usage. The size of a packed non-delta object may be
1326 much larger than the size of objects which delta against it, but the
1327 choice of which object is the base and which is the delta is arbitrary
1328 and is subject to change during a repack.
</p></div>
1329 <div class=
"paragraph"><p>Note also that multiple copies of an object may be present in the object
1330 database; in this case, it is undefined which copy
’s size or delta base
1331 will be reported.
</p></div>
1335 <h2 id=
"_git">GIT
</h2>
1336 <div class=
"sectionbody">
1337 <div class=
"paragraph"><p>Part of the
<a href=
"git.html">git(
1)
</a> suite
</p></div>
1341 <div id=
"footnotes"><hr /></div>
1343 <div id=
"footer-text">
1345 2023-
10-
18 13:
44:
22 PDT