215a7ad1ef
As promised, this is the "big tool rename" patch. The primary differences
since 0.99.6 are:
(1) git-*-script are no more. The commands installed do not
have any such suffix so users do not have to remember if
something is implemented as a shell script or not.
(2) Many command names with 'cache' in them are renamed with
'index' if that is what they mean.
There are backward compatibility symblic links so that you and
Porcelains can keep using the old names, but the backward
compatibility support is expected to be removed in the near
future.
Signed-off-by: Junio C Hamano <junkio@cox.net>
85 lines
2.5 KiB
Plaintext
85 lines
2.5 KiB
Plaintext
git-pack-objects(1)
|
|
===================
|
|
v0.1, July 2005
|
|
|
|
NAME
|
|
----
|
|
git-pack-objects - Create a packed archive of objects.
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
'git-pack-objects' [--incremental] [--window=N] [--depth=N] {--stdout | base-name} < object-list
|
|
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
Reads list of objects from the standard input, and writes a packed
|
|
archive with specified base-name, or to the standard output.
|
|
|
|
A packed archive is an efficient way to transfer set of objects
|
|
between two repositories, and also is an archival format which
|
|
is efficient to access. The packed archive format (.pack) is
|
|
designed to be unpackable without having anything else, but for
|
|
random access, accompanied with the pack index file (.idx).
|
|
|
|
'git-unpack-objects' command can read the packed archive and
|
|
expand the objects contained in the pack into "one-file
|
|
one-object" format; this is typically done by the smart-pull
|
|
commands when a pack is created on-the-fly for efficient network
|
|
transport by their peers.
|
|
|
|
Placing both in the pack/ subdirectory of $GIT_OBJECT_DIRECTORY (or
|
|
any of the directories on $GIT_ALTERNATE_OBJECT_DIRECTORIES)
|
|
enables GIT to read from such an archive.
|
|
|
|
|
|
OPTIONS
|
|
-------
|
|
base-name::
|
|
Write into a pair of files (.pack and .idx), using
|
|
<base-name> to determine the name of the created file.
|
|
When this option is used, the two files are written in
|
|
<base-name>-<SHA1>.{pack,idx} files. <SHA1> is a hash
|
|
of object names (currently in random order so it does
|
|
not have any useful meaning) to make the resulting
|
|
filename reasonably unique, and written to the standard
|
|
output of the command.
|
|
|
|
--stdout::
|
|
Write the pack contents (what would have been writtin to
|
|
.pack file) out to the standard output.
|
|
|
|
--window and --depth::
|
|
These two options affects 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.
|
|
|
|
--incremental::
|
|
This flag causes an object already in a pack ignored
|
|
even if it appears in the standard input.
|
|
|
|
|
|
Author
|
|
------
|
|
Written by Linus Torvalds <torvalds@osdl.org>
|
|
|
|
Documentation
|
|
-------------
|
|
Documentation by Junio C Hamano
|
|
|
|
See-Also
|
|
--------
|
|
git-repack(1) git-prune-packed(1)
|
|
|
|
GIT
|
|
---
|
|
Part of the link:git.html[git] suite
|
|
|