3 # Support routines for hand-crafting weird or malicious packs.
5 # You can make a complete pack like:
7 # pack_header 2 >foo.pack &&
8 # pack_obj e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 >>foo.pack &&
9 # pack_obj e68fe8129b546b101aee9510c5328e7f21ca1d18 >>foo.pack &&
10 # pack_trailer foo.pack
12 # Print the big-endian 4-byte octal representation of $1
15 printf '\%o' $
(($n / 16777216)); n
=$
((n
% 16777216))
16 printf '\%o' $
(($n / 65536)); n
=$
((n
% 65536))
17 printf '\%o' $
(($n / 256)); n
=$
((n
% 256))
18 printf '\%o' $
(($n ));
21 # Print the big-endian 4-byte binary representation of $1
23 printf "$(uint32_octal "$1")"
26 # Print a pack header, version 2, for a pack with $1 objects
33 # Print the pack data for object $1, as a delta against object $2 (or as a full
34 # object if $2 is missing or empty). The output is suitable for including
35 # directly in the packfile, and represents the entirety of the object entry.
36 # Doing this on the fly (especially picking your deltas) is quite tricky, so we
37 # have hardcoded some well-known objects. See the case statements below for the
42 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391
)
45 printf '\060\170\234\003\0\0\0\0\1'
51 # blob containing "\7\76"
52 e68fe8129b546b101aee9510c5328e7f21ca1d18
)
55 printf '\062\170\234\143\267\3\0\0\116\0\106'
62 echo >&2 "BUG: don't know how to print $1${2:+ (from $2)}"
66 # Compute and append pack trailer to "$1"
68 test-sha1
-b <"$1" >trailer.tmp
&&
69 cat trailer.tmp
>>"$1" &&
73 # Remove any existing packs to make sure that
74 # whatever we index next will be the pack that we
77 rm -f .git
/objects
/pack
/*