commands. They are usable but are not meant to compete with real
Porcelains.
-There are also some ancilliary programs that can be viewed as useful
+There are also some ancillary programs that can be viewed as useful
aids for using the core commands but which are unlikely to be used by
SCMs layered over git.
link:git-write-tree.html[git-write-tree]::
Creates a tree from the current cache
+link:git-pack-objects.html[git-pack-objects]::
+ Creates a packed archive of objects.
+
+link:git-prune-packed.html[git-prune-packed]::
+ Remove extra objects that are already in pack files.
+
+
Interrogation commands
~~~~~~~~~~~~~~~~~~~~~~
link:git-cat-file.html[git-cat-file]::
link:git-show-branches-script.html[git-show-branches-script]::
Show branches and their commits.
-Ancilliary Commands
--------------------
+link:git-repack-script.html[git-repack-script]::
+ Pack unpacked objects in a repository.
+
+
+Ancillary Commands
+------------------
Manipulators:
link:git-apply-patch-script.html[git-apply-patch-script]::
An example script to create a tag object signed with GPG
-Interogators:
+Interrogators:
link:git-diff-helper.html[git-diff-helper]::
Generates patch format output for git-diff-*
Symbolic Identifiers
--------------------
-Any git comand accepting any <object> can also use the following
+Any git command accepting any <object> can also use the following
symbolic notation:
HEAD::
'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
Due to the immutable nature of git objects, old objects can be
archived into shared, read-only directories. This variable
- specifies a ":" seperated list of git object directories which
+ specifies a ":" separated list of git object directories which
can be used to search for git objects. New objects will not be
written to these directories.