logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

git-cat-file.1 (17276B)


  1. '\" t
  2. .\" Title: git-cat-file
  3. .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
  4. .\" Generator: DocBook XSL Stylesheets v1.79.2 <http://docbook.sf.net/>
  5. .\" Date: 2025-03-14
  6. .\" Manual: Git Manual
  7. .\" Source: Git 2.49.0
  8. .\" Language: English
  9. .\"
  10. .TH "GIT\-CAT\-FILE" "1" "2025-03-14" "Git 2\&.49\&.0" "Git Manual"
  11. .\" -----------------------------------------------------------------
  12. .\" * Define some portability stuff
  13. .\" -----------------------------------------------------------------
  14. .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  15. .\" http://bugs.debian.org/507673
  16. .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
  17. .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  18. .ie \n(.g .ds Aq \(aq
  19. .el .ds Aq '
  20. .\" -----------------------------------------------------------------
  21. .\" * set default formatting
  22. .\" -----------------------------------------------------------------
  23. .\" disable hyphenation
  24. .nh
  25. .\" disable justification (adjust text to left margin only)
  26. .ad l
  27. .\" -----------------------------------------------------------------
  28. .\" * MAIN CONTENT STARTS HERE *
  29. .\" -----------------------------------------------------------------
  30. .SH "NAME"
  31. git-cat-file \- Provide contents or details of repository objects
  32. .SH "SYNOPSIS"
  33. .sp
  34. .nf
  35. \fIgit cat\-file\fR <type> <object>
  36. \fIgit cat\-file\fR (\-e | \-p) <object>
  37. \fIgit cat\-file\fR (\-t | \-s) [\-\-allow\-unknown\-type] <object>
  38. \fIgit cat\-file\fR (\-\-textconv | \-\-filters)
  39. [<rev>:<path|tree\-ish> | \-\-path=<path|tree\-ish> <rev>]
  40. \fIgit cat\-file\fR (\-\-batch | \-\-batch\-check | \-\-batch\-command) [\-\-batch\-all\-objects]
  41. [\-\-buffer] [\-\-follow\-symlinks] [\-\-unordered]
  42. [\-\-textconv | \-\-filters] [\-Z]
  43. .fi
  44. .SH "DESCRIPTION"
  45. .sp
  46. Output the contents or other properties such as size, type or delta information of one or more objects\&.
  47. .sp
  48. This command can operate in two modes, depending on whether an option from the \fB\-\-batch\fR family is specified\&.
  49. .sp
  50. In non\-batch mode, the command provides information on an object named on the command line\&.
  51. .sp
  52. In batch mode, arguments are read from standard input\&.
  53. .SH "OPTIONS"
  54. .PP
  55. <object>
  56. .RS 4
  57. The name of the object to show\&. For a more complete list of ways to spell object names, see the "SPECIFYING REVISIONS" section in
  58. \fBgitrevisions\fR(7)\&.
  59. .RE
  60. .PP
  61. \-t
  62. .RS 4
  63. Instead of the content, show the object type identified by
  64. \fI<object>\fR\&.
  65. .RE
  66. .PP
  67. \-s
  68. .RS 4
  69. Instead of the content, show the object size identified by
  70. \fI<object>\fR\&. If used with
  71. \fB\-\-use\-mailmap\fR
  72. option, will show the size of updated object after replacing idents using the mailmap mechanism\&.
  73. .RE
  74. .PP
  75. \-e
  76. .RS 4
  77. Exit with zero status if
  78. \fI<object>\fR
  79. exists and is a valid object\&. If
  80. \fI<object>\fR
  81. is of an invalid format, exit with non\-zero status and emit an error on stderr\&.
  82. .RE
  83. .PP
  84. \-p
  85. .RS 4
  86. Pretty\-print the contents of
  87. \fI<object>\fR
  88. based on its type\&.
  89. .RE
  90. .PP
  91. <type>
  92. .RS 4
  93. Typically this matches the real type of
  94. \fI<object>\fR
  95. but asking for a type that can trivially be dereferenced from the given
  96. \fI<object>\fR
  97. is also permitted\&. An example is to ask for a "tree" with
  98. \fI<object>\fR
  99. being a commit object that contains it, or to ask for a "blob" with
  100. \fI<object>\fR
  101. being a tag object that points at it\&.
  102. .RE
  103. .PP
  104. \-\-[no\-]mailmap, \-\-[no\-]use\-mailmap
  105. .RS 4
  106. Use mailmap file to map author, committer and tagger names and email addresses to canonical real names and email addresses\&. See
  107. \fBgit-shortlog\fR(1)\&.
  108. .RE
  109. .PP
  110. \-\-textconv
  111. .RS 4
  112. Show the content as transformed by a textconv filter\&. In this case,
  113. \fI<object>\fR
  114. has to be of the form
  115. \fI<tree\-ish>\fR\fB:\fR\fI<path>\fR, or
  116. \fB:\fR\fI<path>\fR
  117. in order to apply the filter to the content recorded in the index at
  118. \fI<path>\fR\&.
  119. .RE
  120. .PP
  121. \-\-filters
  122. .RS 4
  123. Show the content as converted by the filters configured in the current working tree for the given
  124. \fI<path>\fR
  125. (i\&.e\&. smudge filters, end\-of\-line conversion, etc)\&. In this case,
  126. \fI<object>\fR
  127. has to be of the form
  128. \fI<tree\-ish>\fR\fB:\fR\fI<path>\fR, or
  129. \fB:\fR\fI<path>\fR\&.
  130. .RE
  131. .PP
  132. \-\-path=<path>
  133. .RS 4
  134. For use with
  135. \fB\-\-textconv\fR
  136. or
  137. \fB\-\-filters\fR, to allow specifying an object name and a path separately, e\&.g\&. when it is difficult to figure out the revision from which the blob came\&.
  138. .RE
  139. .PP
  140. \-\-batch, \-\-batch=<format>
  141. .RS 4
  142. Print object information and contents for each object provided on stdin\&. May not be combined with any other options or arguments except
  143. \fB\-\-textconv\fR,
  144. \fB\-\-filters\fR, or
  145. \fB\-\-use\-mailmap\fR\&.
  146. .sp
  147. .RS 4
  148. .ie n \{\
  149. \h'-04'\(bu\h'+03'\c
  150. .\}
  151. .el \{\
  152. .sp -1
  153. .IP \(bu 2.3
  154. .\}
  155. When used with
  156. \fB\-\-textconv\fR
  157. or
  158. \fB\-\-filters\fR, the input lines must specify the path, separated by whitespace\&. See the section
  159. \fBBATCH\fR
  160. \fBOUTPUT\fR
  161. below for details\&.
  162. .RE
  163. .sp
  164. .RS 4
  165. .ie n \{\
  166. \h'-04'\(bu\h'+03'\c
  167. .\}
  168. .el \{\
  169. .sp -1
  170. .IP \(bu 2.3
  171. .\}
  172. When used with
  173. \fB\-\-use\-mailmap\fR, for commit and tag objects, the contents part of the output shows the identities replaced using the mailmap mechanism, while the information part of the output shows the size of the object as if it actually recorded the replacement identities\&.
  174. .RE
  175. .RE
  176. .PP
  177. \-\-batch\-check, \-\-batch\-check=<format>
  178. .RS 4
  179. Print object information for each object provided on stdin\&. May not be combined with any other options or arguments except
  180. \fB\-\-textconv\fR,
  181. \fB\-\-filters\fR
  182. or
  183. \fB\-\-use\-mailmap\fR\&.
  184. .sp
  185. .RS 4
  186. .ie n \{\
  187. \h'-04'\(bu\h'+03'\c
  188. .\}
  189. .el \{\
  190. .sp -1
  191. .IP \(bu 2.3
  192. .\}
  193. When used with
  194. \fB\-\-textconv\fR
  195. or
  196. \fB\-\-filters\fR, the input lines must specify the path, separated by whitespace\&. See the section
  197. \fBBATCH\fR
  198. \fBOUTPUT\fR
  199. below for details\&.
  200. .RE
  201. .sp
  202. .RS 4
  203. .ie n \{\
  204. \h'-04'\(bu\h'+03'\c
  205. .\}
  206. .el \{\
  207. .sp -1
  208. .IP \(bu 2.3
  209. .\}
  210. When used with
  211. \fB\-\-use\-mailmap\fR, for commit and tag objects, the printed object information shows the size of the object as if the identities recorded in it were replaced by the mailmap mechanism\&.
  212. .RE
  213. .RE
  214. .PP
  215. \-\-batch\-command, \-\-batch\-command=<format>
  216. .RS 4
  217. Enter a command mode that reads commands and arguments from stdin\&. May only be combined with
  218. \fB\-\-buffer\fR,
  219. \fB\-\-textconv\fR,
  220. \fB\-\-use\-mailmap\fR
  221. or
  222. \fB\-\-filters\fR\&.
  223. .sp
  224. .RS 4
  225. .ie n \{\
  226. \h'-04'\(bu\h'+03'\c
  227. .\}
  228. .el \{\
  229. .sp -1
  230. .IP \(bu 2.3
  231. .\}
  232. When used with
  233. \fB\-\-textconv\fR
  234. or
  235. \fB\-\-filters\fR, the input lines must specify the path, separated by whitespace\&. See the section
  236. \fBBATCH\fR
  237. \fBOUTPUT\fR
  238. below for details\&.
  239. .RE
  240. .sp
  241. .RS 4
  242. .ie n \{\
  243. \h'-04'\(bu\h'+03'\c
  244. .\}
  245. .el \{\
  246. .sp -1
  247. .IP \(bu 2.3
  248. .\}
  249. When used with
  250. \fB\-\-use\-mailmap\fR, for commit and tag objects, the
  251. \fBcontents\fR
  252. command shows the identities replaced using the mailmap mechanism, while the
  253. \fBinfo\fR
  254. command shows the size of the object as if it actually recorded the replacement identities\&.
  255. .RE
  256. .sp
  257. \fB\-\-batch\-command\fR
  258. recognizes the following commands:
  259. .PP
  260. contents <object>
  261. .RS 4
  262. Print object contents for object reference
  263. \fI<object>\fR\&. This corresponds to the output of
  264. \fB\-\-batch\fR\&.
  265. .RE
  266. .PP
  267. info <object>
  268. .RS 4
  269. Print object info for object reference
  270. \fI<object>\fR\&. This corresponds to the output of
  271. \fB\-\-batch\-check\fR\&.
  272. .RE
  273. .PP
  274. flush
  275. .RS 4
  276. Used with
  277. \fB\-\-buffer\fR
  278. to execute all preceding commands that were issued since the beginning or since the last flush was issued\&. When
  279. \fB\-\-buffer\fR
  280. is used, no output will come until a
  281. \fBflush\fR
  282. is issued\&. When
  283. \fB\-\-buffer\fR
  284. is not used, commands are flushed each time without issuing
  285. \fBflush\fR\&.
  286. .RE
  287. .RE
  288. .PP
  289. \-\-batch\-all\-objects
  290. .RS 4
  291. Instead of reading a list of objects on stdin, perform the requested batch operation on all objects in the repository and any alternate object stores (not just reachable objects)\&. Requires
  292. \fB\-\-batch\fR
  293. or
  294. \fB\-\-batch\-check\fR
  295. be specified\&. By default, the objects are visited in order sorted by their hashes; see also
  296. \fB\-\-unordered\fR
  297. below\&. Objects are presented as\-is, without respecting the "replace" mechanism of
  298. \fBgit-replace\fR(1)\&.
  299. .RE
  300. .PP
  301. \-\-buffer
  302. .RS 4
  303. Normally batch output is flushed after each object is output, so that a process can interactively read and write from
  304. \fBcat\-file\fR\&. With this option, the output uses normal stdio buffering; this is much more efficient when invoking
  305. \fB\-\-batch\-check\fR
  306. or
  307. \fB\-\-batch\-command\fR
  308. on a large number of objects\&.
  309. .RE
  310. .PP
  311. \-\-unordered
  312. .RS 4
  313. When
  314. \fB\-\-batch\-all\-objects\fR
  315. is in use, visit objects in an order which may be more efficient for accessing the object contents than hash order\&. The exact details of the order are unspecified, but if you do not require a specific order, this should generally result in faster output, especially with
  316. \fB\-\-batch\fR\&. Note that
  317. \fBcat\-file\fR
  318. will still show each object only once, even if it is stored multiple times in the repository\&.
  319. .RE
  320. .PP
  321. \-\-allow\-unknown\-type
  322. .RS 4
  323. Allow
  324. \fB\-s\fR
  325. or
  326. \fB\-t\fR
  327. to query broken/corrupt objects of unknown type\&.
  328. .RE
  329. .PP
  330. \-\-follow\-symlinks
  331. .RS 4
  332. With
  333. \fB\-\-batch\fR
  334. or
  335. \fB\-\-batch\-check\fR, follow symlinks inside the repository when requesting objects with extended SHA\-1 expressions of the form tree\-ish:path\-in\-tree\&. Instead of providing output about the link itself, provide output about the linked\-to object\&. If a symlink points outside the tree\-ish (e\&.g\&. a link to
  336. \fB/foo\fR
  337. or a root\-level link to
  338. \fB\&.\&.\fR\fB/foo\fR), the portion of the link which is outside the tree will be printed\&.
  339. .sp
  340. This option does not (currently) work correctly when an object in the index is specified (e\&.g\&.
  341. \fB:link\fR
  342. instead of
  343. \fBHEAD:link\fR) rather than one in the tree\&.
  344. .sp
  345. This option cannot (currently) be used unless
  346. \fB\-\-batch\fR
  347. or
  348. \fB\-\-batch\-check\fR
  349. is used\&.
  350. .sp
  351. For example, consider a git repository containing:
  352. .sp
  353. .if n \{\
  354. .RS 4
  355. .\}
  356. .nf
  357. f: a file containing "hello\en"
  358. link: a symlink to f
  359. dir/link: a symlink to \&.\&./f
  360. plink: a symlink to \&.\&./f
  361. alink: a symlink to /etc/passwd
  362. .fi
  363. .if n \{\
  364. .RE
  365. .\}
  366. .sp
  367. For a regular file
  368. \fBf\fR,
  369. \fBecho\fR
  370. \fBHEAD:f\fR
  371. |
  372. \fBgit\fR
  373. \fBcat\-file\fR
  374. \fB\-\-batch\fR
  375. would print
  376. .sp
  377. .if n \{\
  378. .RS 4
  379. .\}
  380. .nf
  381. ce013625030ba8dba906f756967f9e9ca394464a blob 6
  382. .fi
  383. .if n \{\
  384. .RE
  385. .\}
  386. .sp
  387. And
  388. \fBecho\fR
  389. \fBHEAD:link\fR
  390. |
  391. \fBgit\fR
  392. \fBcat\-file\fR
  393. \fB\-\-batch\fR
  394. \fB\-\-follow\-symlinks\fR
  395. would print the same thing, as would
  396. \fBHEAD:dir/link\fR, as they both point at
  397. \fBHEAD:f\fR\&.
  398. .sp
  399. Without
  400. \fB\-\-follow\-symlinks\fR, these would print data about the symlink itself\&. In the case of
  401. \fBHEAD:link\fR, you would see
  402. .sp
  403. .if n \{\
  404. .RS 4
  405. .\}
  406. .nf
  407. 4d1ae35ba2c8ec712fa2a379db44ad639ca277bd blob 1
  408. .fi
  409. .if n \{\
  410. .RE
  411. .\}
  412. .sp
  413. Both
  414. \fBplink\fR
  415. and
  416. \fBalink\fR
  417. point outside the tree, so they would respectively print:
  418. .sp
  419. .if n \{\
  420. .RS 4
  421. .\}
  422. .nf
  423. symlink 4
  424. \&.\&./f
  425. .fi
  426. .if n \{\
  427. .RE
  428. .\}
  429. .sp
  430. .if n \{\
  431. .RS 4
  432. .\}
  433. .nf
  434. symlink 11
  435. /etc/passwd
  436. .fi
  437. .if n \{\
  438. .RE
  439. .\}
  440. .RE
  441. .PP
  442. \-Z
  443. .RS 4
  444. Only meaningful with
  445. \fB\-\-batch\fR,
  446. \fB\-\-batch\-check\fR, or
  447. \fB\-\-batch\-command\fR; input and output is NUL\-delimited instead of newline\-delimited\&.
  448. .RE
  449. .PP
  450. \-z
  451. .RS 4
  452. Only meaningful with
  453. \fB\-\-batch\fR,
  454. \fB\-\-batch\-check\fR, or
  455. \fB\-\-batch\-command\fR; input is NUL\-delimited instead of newline\-delimited\&. This option is deprecated in favor of
  456. \fB\-Z\fR
  457. as the output can otherwise be ambiguous\&.
  458. .RE
  459. .SH "OUTPUT"
  460. .sp
  461. If \fB\-t\fR is specified, one of the \fI<type>\fR\&.
  462. .sp
  463. If \fB\-s\fR is specified, the size of the \fI<object>\fR in bytes\&.
  464. .sp
  465. If \fB\-e\fR is specified, no output, unless the \fI<object>\fR is malformed\&.
  466. .sp
  467. If \fB\-p\fR is specified, the contents of \fI<object>\fR are pretty\-printed\&.
  468. .sp
  469. If \fI<type>\fR is specified, the raw (though uncompressed) contents of the \fI<object>\fR will be returned\&.
  470. .SH "BATCH OUTPUT"
  471. .sp
  472. If \fB\-\-batch\fR or \fB\-\-batch\-check\fR is given, \fBcat\-file\fR will read objects from stdin, one per line, and print information about them in the same order as they have been read\&. By default, the whole line is considered as an object, as if it were fed to \fBgit-rev-parse\fR(1)\&.
  473. .sp
  474. When \fB\-\-batch\-command\fR is given, \fBcat\-file\fR will read commands from stdin, one per line, and print information based on the command given\&. With \fB\-\-batch\-command\fR, the \fBinfo\fR command followed by an object will print information about the object the same way \fB\-\-batch\-check\fR would, and the \fBcontents\fR command followed by an object prints contents in the same way \fB\-\-batch\fR would\&.
  475. .sp
  476. You can specify the information shown for each object by using a custom \fI<format>\fR\&. The \fI<format>\fR is copied literally to stdout for each object, with placeholders of the form %(\fBatom\fR) expanded, followed by a newline\&. The available atoms are:
  477. .PP
  478. \fBobjectname\fR
  479. .RS 4
  480. The full hex representation of the object name\&.
  481. .RE
  482. .PP
  483. \fBobjecttype\fR
  484. .RS 4
  485. The type of the object (the same as
  486. \fBcat\-file\fR
  487. \fB\-t\fR
  488. reports)\&.
  489. .RE
  490. .PP
  491. \fBobjectsize\fR
  492. .RS 4
  493. The size, in bytes, of the object (the same as
  494. \fBcat\-file\fR
  495. \fB\-s\fR
  496. reports)\&.
  497. .RE
  498. .PP
  499. \fBobjectsize:disk\fR
  500. .RS 4
  501. The size, in bytes, that the object takes up on disk\&. See the note about on\-disk sizes in the
  502. \fBCAVEATS\fR
  503. section below\&.
  504. .RE
  505. .PP
  506. \fBdeltabase\fR
  507. .RS 4
  508. If the object is stored as a delta on\-disk, this expands to the full hex representation of the delta base object name\&. Otherwise, expands to the null OID (all zeroes)\&. See
  509. \fBCAVEATS\fR
  510. below\&.
  511. .RE
  512. .PP
  513. \fBrest\fR
  514. .RS 4
  515. If this atom is used in the output string, input lines are split at the first whitespace boundary\&. All characters before that whitespace are considered to be the object name; characters after that first run of whitespace (i\&.e\&., the "rest" of the line) are output in place of the %(\fBrest\fR) atom\&.
  516. .RE
  517. .sp
  518. If no format is specified, the default format is %(\fBobjectname\fR) %(\fBobjecttype\fR) %(\fBobjectsize\fR)\&.
  519. .sp
  520. If \fB\-\-batch\fR is specified, or if \fB\-\-batch\-command\fR is used with the \fBcontents\fR command, the object information is followed by the object contents (consisting of %(\fBobjectsize\fR) bytes), followed by a newline\&.
  521. .sp
  522. For example, \fB\-\-batch\fR without a custom format would produce:
  523. .sp
  524. .if n \{\
  525. .RS 4
  526. .\}
  527. .nf
  528. <oid> SP <type> SP <size> LF
  529. <contents> LF
  530. .fi
  531. .if n \{\
  532. .RE
  533. .\}
  534. .sp
  535. Whereas \fB\-\-batch\-check=\fR\*(Aq%(\fBobjectname\fR) %(\fBobjecttype\fR)\*(Aq would produce:
  536. .sp
  537. .if n \{\
  538. .RS 4
  539. .\}
  540. .nf
  541. <oid> SP <type> LF
  542. .fi
  543. .if n \{\
  544. .RE
  545. .\}
  546. .sp
  547. If a name is specified on stdin that cannot be resolved to an object in the repository, then \fBcat\-file\fR will ignore any custom format and print:
  548. .sp
  549. .if n \{\
  550. .RS 4
  551. .\}
  552. .nf
  553. <object> SP missing LF
  554. .fi
  555. .if n \{\
  556. .RE
  557. .\}
  558. .sp
  559. If a name is specified that might refer to more than one object (an ambiguous short sha), then \fBcat\-file\fR will ignore any custom format and print:
  560. .sp
  561. .if n \{\
  562. .RS 4
  563. .\}
  564. .nf
  565. <object> SP ambiguous LF
  566. .fi
  567. .if n \{\
  568. .RE
  569. .\}
  570. .sp
  571. If \fB\-\-follow\-symlinks\fR is used, and a symlink in the repository points outside the repository, then \fBcat\-file\fR will ignore any custom format and print:
  572. .sp
  573. .if n \{\
  574. .RS 4
  575. .\}
  576. .nf
  577. symlink SP <size> LF
  578. <symlink> LF
  579. .fi
  580. .if n \{\
  581. .RE
  582. .\}
  583. .sp
  584. The symlink will either be absolute (beginning with a \fB/\fR), or relative to the tree root\&. For instance, if dir/link points to \fB\&.\&.\fR\fB/\fR\fB\&.\&.\fR\fB/foo\fR, then \fI<symlink>\fR will be \fB\&.\&.\fR\fB/foo\fR\&. \fI<size>\fR is the size of the symlink in bytes\&.
  585. .sp
  586. If \fB\-\-follow\-symlinks\fR is used, the following error messages will be displayed:
  587. .sp
  588. .if n \{\
  589. .RS 4
  590. .\}
  591. .nf
  592. <object> SP missing LF
  593. .fi
  594. .if n \{\
  595. .RE
  596. .\}
  597. .sp
  598. is printed when the initial symlink requested does not exist\&.
  599. .sp
  600. .if n \{\
  601. .RS 4
  602. .\}
  603. .nf
  604. dangling SP <size> LF
  605. <object> LF
  606. .fi
  607. .if n \{\
  608. .RE
  609. .\}
  610. .sp
  611. is printed when the initial symlink exists, but something that it (transitive\-of) points to does not\&.
  612. .sp
  613. .if n \{\
  614. .RS 4
  615. .\}
  616. .nf
  617. loop SP <size> LF
  618. <object> LF
  619. .fi
  620. .if n \{\
  621. .RE
  622. .\}
  623. .sp
  624. is printed for symlink loops (or any symlinks that require more than 40 link resolutions to resolve)\&.
  625. .sp
  626. .if n \{\
  627. .RS 4
  628. .\}
  629. .nf
  630. notdir SP <size> LF
  631. <object> LF
  632. .fi
  633. .if n \{\
  634. .RE
  635. .\}
  636. .sp
  637. is printed when, during symlink resolution, a file is used as a directory name\&.
  638. .sp
  639. Alternatively, when \fB\-Z\fR is passed, the line feeds in any of the above examples are replaced with NUL terminators\&. This ensures that output will be parsable if the output itself would contain a linefeed and is thus recommended for scripting purposes\&.
  640. .SH "CAVEATS"
  641. .sp
  642. Note that the sizes of objects on disk are reported accurately, but care should be taken in drawing conclusions about which refs or objects are responsible for disk usage\&. The size of a packed non\-delta object may be much larger than the size of objects which delta against it, but the choice of which object is the base and which is the delta is arbitrary and is subject to change during a repack\&.
  643. .sp
  644. Note also that multiple copies of an object may be present in the object database; in this case, it is undefined which copy\(cqs size or delta base will be reported\&.
  645. .SH "GIT"
  646. .sp
  647. Part of the \fBgit\fR(1) suite