{ "content": [ { "type": "text", "text": "# GIT-REPACK (man)\n\n## NAME\n\ngit-repack - Pack unpacked objects in a repository\n\n## SYNOPSIS\n\ngit repack [-a] [-A] [-d] [-f] [-F] [-l] [-n] [-q] [-b] [-m] [--window=] [--depth=] [--threads=] [--keep-pack=] [--write-midx]\n\n## DESCRIPTION\n\nThis command is used to combine all objects that do not currently reside in a \"pack\", into a\npack. It can also be used to re-organize existing packs into a single, more efficient pack.\n\n## TLDR\n\n> Pack unpacked objects in a Git repository.\n\n- Pack unpacked objects in the current directory:\n `git repack`\n- Remove redundant objects after packing:\n `git repack -d`\n- Repack all objects into a single pack:\n `git repack -a`\n- Limit the repack to local objects only:\n `git repack -l`\n\n*Source: tldr-pages*\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS** (13 subsections)\n- **CONFIGURATION**\n- **SEE ALSO**\n- **GIT**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "GIT-REPACK", "section": "", "mode": "man", "summary": "git-repack - Pack unpacked objects in a repository", "synopsis": "git repack [-a] [-A] [-d] [-f] [-F] [-l] [-n] [-q] [-b] [-m] [--window=] [--depth=] [--threads=] [--keep-pack=] [--write-midx]", "tldr_summary": "Pack unpacked objects in a Git repository.", "tldr_examples": [ { "description": "Pack unpacked objects in the current directory", "command": "git repack" }, { "description": "Remove redundant objects after packing", "command": "git repack -d" }, { "description": "Repack all objects into a single pack", "command": "git repack -a" }, { "description": "Limit the repack to local objects only", "command": "git repack -l" } ], "tldr_source": "official", "flags": [ { "flag": "-a", "long": null, "arg": null, "description": "Instead of incrementally packing the unpacked objects, pack everything referenced into a single pack. Especially useful when packing a repository that is used for private development. Use with -d. This will clean up the objects that git prune leaves behind, but git fsck --full --dangling shows as dangling. Note that users fetching over dumb protocols will have to fetch the whole new pack in order to get any contained object, no matter how many other objects in that pack they already have locally. Promisor packfiles are repacked separately: if there are packfiles that have an associated \".promisor\" file, these packfiles will be repacked into another separate pack, and an empty \".promisor\" file corresponding to the new separate pack will be written." }, { "flag": "-A", "long": null, "arg": null, "description": "Same as -a, unless -d is used. Then any unreachable objects in a previous pack become loose, unpacked objects, instead of being left in the old pack. Unreachable objects are never intentionally added to a pack, even when repacking. This option prevents unreachable objects from being immediately deleted by way of being left in the old pack and then removed. Instead, the loose unreachable objects will be pruned according to normal expiry rules with the next git gc invocation. See git-gc(1)." }, { "flag": "-d", "long": null, "arg": null, "description": "After packing, if the newly created packs make some existing packs redundant, remove the redundant packs. Also run git prune-packed to remove redundant loose object files." }, { "flag": "-l", "long": null, "arg": null, "description": "Pass the --local option to git pack-objects. See git-pack-objects(1)." }, { "flag": "-f", "long": null, "arg": null, "description": "Pass the --no-reuse-delta option to git-pack-objects, see git-pack-objects(1)." }, { "flag": "-F", "long": null, "arg": null, "description": "Pass the --no-reuse-object option to git-pack-objects, see git-pack-objects(1)." }, { "flag": "-q", "long": null, "arg": null, "description": "Pass the -q option to git pack-objects. See git-pack-objects(1)." }, { "flag": "-n", "long": null, "arg": null, "description": "Do not update the server information with git update-server-info. This option skips updating local catalog files needed to publish this repository (or a direct copy of it) over HTTP or FTP. See git-update-server-info(1). --window=, --depth= These two options affect how the objects contained in the pack are stored using delta compression. The objects are first internally sorted by type, size and optionally names and compared against the other objects within --window to see if using delta compression saves space. --depth limits the maximum delta depth; making it too deep affects the performance on the unpacker side, because delta data needs to be applied that many times to get to the necessary object. The default value for --window is 10 and --depth is 50. The maximum depth is 4095. --threads= This option is passed through to git pack-objects. --window-memory= This option provides an additional limit on top of --window; the window size will dynamically scale down so as to not take up more than bytes in memory. This is useful in repositories with a mix of large and small objects to not run out of memory with a large window, but still be able to take advantage of the large window for the smaller objects. The size can be suffixed with \"k\", \"m\", or \"g\". --window-memory=0 makes memory usage unlimited. The default is taken from the pack.windowMemory configuration variable. Note that the actual memory usage will be the limit multiplied by the number of threads used by git-pack-objects(1). --max-pack-size= Maximum size of each output pack file. The size can be suffixed with \"k\", \"m\", or \"g\". The minimum size allowed is limited to 1 MiB. If specified, multiple packfiles may be created, which also prevents the creation of a bitmap index. The default is unlimited, unless the config variable pack.packSizeLimit is set. Note that this option may result in a larger and slower repository; see the discussion in pack.packSizeLimit." }, { "flag": "-b", "long": "--write-bitmap-index", "arg": null, "description": "Write a reachability bitmap index as part of the repack. This only makes sense when used with -a, -A or -m, as the bitmaps must be able to refer to all reachable objects. This option overrides the setting of repack.writeBitmaps. This option has no effect if multiple packfiles are created, unless writing a MIDX (in which case a multi-pack bitmap is created)." }, { "flag": "", "long": "--pack-kept-objects", "arg": null, "description": "Include objects in .keep files when repacking. Note that we still do not delete .keep packs after pack-objects finishes. This means that we may duplicate objects, but this makes the option safe to use when there are concurrent pushes or fetches. This option is generally only useful if you are writing bitmaps with -b or repack.writeBitmaps, as it ensures that the bitmapped packfile has the necessary objects. --keep-pack= Exclude the given pack from repacking. This is the equivalent of having .keep file on the pack. is the pack file name without leading directory (e.g. pack-123.pack). The option could be specified multiple times to keep multiple packs. --unpack-unreachable= When loosening unreachable objects, do not bother loosening any objects older than . This can be used to optimize out the write of any objects that would be immediately pruned by a follow-up git prune." }, { "flag": "-k", "long": "--keep-unreachable", "arg": null, "description": "When used with -ad, any unreachable objects from existing packs will be appended to the end of the packfile instead of being removed. In addition, any unreachable loose objects will be packed (and their loose counterparts removed)." }, { "flag": "-i", "long": "--delta-islands", "arg": null, "description": "Pass the --delta-islands option to git-pack-objects, see git-pack-objects(1). -g=, --geometric= Arrange resulting pack structure so that each successive pack contains at least times the number of objects as the next-largest pack. git repack ensures this by determining a \"cut\" of packfiles that need to be repacked into one in order to ensure a geometric progression. It picks the smallest set of packfiles such that as many of the larger packfiles (by count of objects contained in that pack) may be left intact. Unlike other repack modes, the set of objects to pack is determined uniquely by the set of packs being \"rolled-up\"; in other words, the packs determined to need to be combined in order to restore a geometric progression. When --unpacked is specified, loose objects are implicitly included in this \"roll-up\", without respect to their reachability. This is subject to change in the future. This option (implying a drastically different repack mode) is not guaranteed to work with all other combinations of option to git repack. When writing a multi-pack bitmap, git repack selects the largest resulting pack as the preferred pack for object selection by the MIDX (see git-multi-pack-index(1))." }, { "flag": "-m", "long": "--write-midx", "arg": null, "description": "Write a multi-pack index (see git-multi-pack-index(1)) containing the non-redundant packs." } ], "examples": [], "see_also": [ { "name": "git-pack-objects", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/git-pack-objects/1/json" }, { "name": "git-prune-packed", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/git-prune-packed/1/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 3, "subsections": [] }, { "name": "DESCRIPTION", "lines": 8, "subsections": [] }, { "name": "OPTIONS", "lines": 1, "subsections": [ { "name": "-a", "lines": 13, "flag": "-a" }, { "name": "-A", "lines": 7, "flag": "-A" }, { "name": "-d", "lines": 3, "flag": "-d" }, { "name": "-l", "lines": 2, "flag": "-l" }, { "name": "-f", "lines": 2, "flag": "-f" }, { "name": "-F", "lines": 2, "flag": "-F" }, { "name": "-q", "lines": 2, "flag": "-q" }, { "name": "-n", "lines": 34, "flag": "-n" }, { "name": "-b, --write-bitmap-index", "lines": 6, "flag": "-b", "long": "--write-bitmap-index" }, { "name": "--pack-kept-objects", "lines": 16, "long": "--pack-kept-objects" }, { "name": "-k, --keep-unreachable", "lines": 4, "flag": "-k", "long": "--keep-unreachable" }, { "name": "-i, --delta-islands", "lines": 23, "flag": "-i", "long": "--delta-islands" }, { "name": "-m, --write-midx", "lines": 3, "flag": "-m", "long": "--write-midx" } ] }, { "name": "CONFIGURATION", "lines": 14, "subsections": [] }, { "name": "SEE ALSO", "lines": 2, "subsections": [] }, { "name": "GIT", "lines": 5, "subsections": [] } ], "sections": { "NAME": { "content": "git-repack - Pack unpacked objects in a repository\n", "subsections": [] }, "SYNOPSIS": { "content": "git repack [-a] [-A] [-d] [-f] [-F] [-l] [-n] [-q] [-b] [-m] [--window=] [--depth=] [--threads=] [--keep-pack=] [--write-midx]\n\n", "subsections": [] }, "DESCRIPTION": { "content": "This command is used to combine all objects that do not currently reside in a \"pack\", into a\npack. It can also be used to re-organize existing packs into a single, more efficient pack.\n\nA pack is a collection of objects, individually compressed, with delta compression applied,\nstored in a single file, with an associated index file.\n\nPacks are used to reduce the load on mirror systems, backup engines, disk storage, etc.\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": "-a", "content": "Instead of incrementally packing the unpacked objects, pack everything referenced into a\nsingle pack. Especially useful when packing a repository that is used for private\ndevelopment. Use with -d. This will clean up the objects that git prune leaves behind,\nbut git fsck --full --dangling shows as dangling.\n\nNote that users fetching over dumb protocols will have to fetch the whole new pack in\norder to get any contained object, no matter how many other objects in that pack they\nalready have locally.\n\nPromisor packfiles are repacked separately: if there are packfiles that have an\nassociated \".promisor\" file, these packfiles will be repacked into another separate pack,\nand an empty \".promisor\" file corresponding to the new separate pack will be written.\n", "flag": "-a" }, { "name": "-A", "content": "Same as -a, unless -d is used. Then any unreachable objects in a previous pack become\nloose, unpacked objects, instead of being left in the old pack. Unreachable objects are\nnever intentionally added to a pack, even when repacking. This option prevents\nunreachable objects from being immediately deleted by way of being left in the old pack\nand then removed. Instead, the loose unreachable objects will be pruned according to\nnormal expiry rules with the next git gc invocation. See git-gc(1).\n", "flag": "-A" }, { "name": "-d", "content": "After packing, if the newly created packs make some existing packs redundant, remove the\nredundant packs. Also run git prune-packed to remove redundant loose object files.\n", "flag": "-d" }, { "name": "-l", "content": "Pass the --local option to git pack-objects. See git-pack-objects(1).\n", "flag": "-l" }, { "name": "-f", "content": "Pass the --no-reuse-delta option to git-pack-objects, see git-pack-objects(1).\n", "flag": "-f" }, { "name": "-F", "content": "Pass the --no-reuse-object option to git-pack-objects, see git-pack-objects(1).\n", "flag": "-F" }, { "name": "-q", "content": "Pass the -q option to git pack-objects. See git-pack-objects(1).\n", "flag": "-q" }, { "name": "-n", "content": "Do not update the server information with git update-server-info. This option skips\nupdating local catalog files needed to publish this repository (or a direct copy of it)\nover HTTP or FTP. See git-update-server-info(1).\n\n--window=, --depth=\nThese two options affect how the objects contained in the pack are stored using delta\ncompression. The objects are first internally sorted by type, size and optionally names\nand compared against the other objects within --window to see if using delta compression\nsaves space. --depth limits the maximum delta depth; making it too deep affects the\nperformance on the unpacker side, because delta data needs to be applied that many times\nto get to the necessary object.\n\nThe default value for --window is 10 and --depth is 50. The maximum depth is 4095.\n\n--threads=\nThis option is passed through to git pack-objects.\n\n--window-memory=\nThis option provides an additional limit on top of --window; the window size will\ndynamically scale down so as to not take up more than bytes in memory. This is useful\nin repositories with a mix of large and small objects to not run out of memory with a\nlarge window, but still be able to take advantage of the large window for the smaller\nobjects. The size can be suffixed with \"k\", \"m\", or \"g\". --window-memory=0 makes memory\nusage unlimited. The default is taken from the pack.windowMemory configuration variable.\nNote that the actual memory usage will be the limit multiplied by the number of threads\nused by git-pack-objects(1).\n\n--max-pack-size=\nMaximum size of each output pack file. The size can be suffixed with \"k\", \"m\", or \"g\".\nThe minimum size allowed is limited to 1 MiB. If specified, multiple packfiles may be\ncreated, which also prevents the creation of a bitmap index. The default is unlimited,\nunless the config variable pack.packSizeLimit is set. Note that this option may result in\na larger and slower repository; see the discussion in pack.packSizeLimit.\n", "flag": "-n" }, { "name": "-b, --write-bitmap-index", "content": "Write a reachability bitmap index as part of the repack. This only makes sense when used\nwith -a, -A or -m, as the bitmaps must be able to refer to all reachable objects. This\noption overrides the setting of repack.writeBitmaps. This option has no effect if\nmultiple packfiles are created, unless writing a MIDX (in which case a multi-pack bitmap\nis created).\n", "flag": "-b", "long": "--write-bitmap-index" }, { "name": "--pack-kept-objects", "content": "Include objects in .keep files when repacking. Note that we still do not delete .keep\npacks after pack-objects finishes. This means that we may duplicate objects, but this\nmakes the option safe to use when there are concurrent pushes or fetches. This option is\ngenerally only useful if you are writing bitmaps with -b or repack.writeBitmaps, as it\nensures that the bitmapped packfile has the necessary objects.\n\n--keep-pack=\nExclude the given pack from repacking. This is the equivalent of having .keep file on the\npack. is the pack file name without leading directory (e.g. pack-123.pack).\nThe option could be specified multiple times to keep multiple packs.\n\n--unpack-unreachable=\nWhen loosening unreachable objects, do not bother loosening any objects older than\n. This can be used to optimize out the write of any objects that would be\nimmediately pruned by a follow-up git prune.\n", "long": "--pack-kept-objects" }, { "name": "-k, --keep-unreachable", "content": "When used with -ad, any unreachable objects from existing packs will be appended to the\nend of the packfile instead of being removed. In addition, any unreachable loose objects\nwill be packed (and their loose counterparts removed).\n", "flag": "-k", "long": "--keep-unreachable" }, { "name": "-i, --delta-islands", "content": "Pass the --delta-islands option to git-pack-objects, see git-pack-objects(1).\n\n-g=, --geometric=\nArrange resulting pack structure so that each successive pack contains at least \ntimes the number of objects as the next-largest pack.\n\ngit repack ensures this by determining a \"cut\" of packfiles that need to be repacked into\none in order to ensure a geometric progression. It picks the smallest set of packfiles\nsuch that as many of the larger packfiles (by count of objects contained in that pack)\nmay be left intact.\n\nUnlike other repack modes, the set of objects to pack is determined uniquely by the set\nof packs being \"rolled-up\"; in other words, the packs determined to need to be combined\nin order to restore a geometric progression.\n\nWhen --unpacked is specified, loose objects are implicitly included in this \"roll-up\",\nwithout respect to their reachability. This is subject to change in the future. This\noption (implying a drastically different repack mode) is not guaranteed to work with all\nother combinations of option to git repack.\n\nWhen writing a multi-pack bitmap, git repack selects the largest resulting pack as the\npreferred pack for object selection by the MIDX (see git-multi-pack-index(1)).\n", "flag": "-i", "long": "--delta-islands" }, { "name": "-m, --write-midx", "content": "Write a multi-pack index (see git-multi-pack-index(1)) containing the non-redundant\npacks.\n", "flag": "-m", "long": "--write-midx" } ] }, "CONFIGURATION": { "content": "Various configuration variables affect packing, see git-config(1) (search for \"pack\" and\n\"delta\").\n\nBy default, the command passes --delta-base-offset option to git pack-objects; this typically\nresults in slightly smaller packs, but the generated packs are incompatible with versions of\nGit older than version 1.4.4. If you need to share your repository with such ancient Git\nversions, either directly or via the dumb http protocol, then you need to set the\nconfiguration variable repack.UseDeltaBaseOffset to \"false\" and repack. Access from old Git\nversions over the native protocol is unaffected by this option as the conversion is performed\non the fly as needed in that case.\n\nDelta compression is not used on objects larger than the core.bigFileThreshold configuration\nvariable and on files with the attribute delta set to false.\n", "subsections": [] }, "SEE ALSO": { "content": "git-pack-objects(1) git-prune-packed(1)\n", "subsections": [] }, "GIT": { "content": "Part of the git(1) suite\n\n\n\nGit 2.34.1 02/26/2026 GIT-REPACK(1)", "subsections": [] } } } }