and might match multiple refs in the .git/refs/ tree. True by default.
core.compression::
+ An integer -1..9, indicating a default compression level.
+ -1 is the zlib default. 0 means no compression,
+ and 1..9 are various speed/size tradeoffs, 9 being slowest.
+
+core.loosecompression::
An integer -1..9, indicating the compression level for objects that
- are not in a pack file. -1 is the zlib and git default. 0 means no
+ are not in a pack file. -1 is the zlib default. 0 means no
compression, and 1..9 are various speed/size tradeoffs, 9 being
- slowest.
-
-core.legacyheaders::
- A boolean which
- changes the format of loose objects so that they are more
- efficient to pack and to send out of the repository over git
- native protocol, since v1.4.2. However, loose objects
- written in the new format cannot be read by git older than
- that version; people fetching from your repository using
- older versions of git over dumb transports (e.g. http)
- will also be affected.
-+
-To let git use the new loose object format, you have to
-set core.legacyheaders to false.
+ slowest. If not set, defaults to core.compression. If that is
+ not set, defaults to 0 (best speed).
core.packedGitWindowSize::
Number of bytes of a pack file to map into memory in a
`.patch`. Use this variable to change that suffix (make sure to
include the dot if you want it).
+gc.aggressiveWindow::
+ The window size parameter used in the delta compression
+ algorithm used by 'git gc --aggressive'. This defaults
+ to 10.
+
gc.packrefs::
`git gc` does not run `git pack-refs` in a bare repository by
default so that older dumb-transport clients can still fetch
The maximum delta depth used by gitlink:git-pack-objects[1] when no
maximum depth is given on the command line. Defaults to 50.
+pack.compression::
+ An integer -1..9, indicating the compression level for objects
+ in a pack file. -1 is the zlib default. 0 means no
+ compression, and 1..9 are various speed/size tradeoffs, 9 being
+ slowest. If not set, defaults to core.compression. If that is
+ not set, defaults to -1.
+
pull.octopus::
The default merge strategy to use when pulling multiple branches
at once.
</dt>\r
<dd>\r
<p>\r
- An integer -1..9, indicating the compression level for objects that\r
- are not in a pack file. -1 is the zlib and git default. 0 means no\r
- compression, and 1..9 are various speed/size tradeoffs, 9 being\r
- slowest.\r
+ An integer -1..9, indicating a default compression level.\r
+ -1 is the zlib default. 0 means no compression,\r
+ and 1..9 are various speed/size tradeoffs, 9 being slowest.\r
</p>\r
</dd>\r
<dt>\r
-core.legacyheaders\r
+core.loosecompression\r
</dt>\r
<dd>\r
<p>\r
- A boolean which\r
- changes the format of loose objects so that they are more\r
- efficient to pack and to send out of the repository over git\r
- native protocol, since v1.4.2. However, loose objects\r
- written in the new format cannot be read by git older than\r
- that version; people fetching from your repository using\r
- older versions of git over dumb transports (e.g. http)\r
- will also be affected.\r
+ An integer -1..9, indicating the compression level for objects that\r
+ are not in a pack file. -1 is the zlib default. 0 means no\r
+ compression, and 1..9 are various speed/size tradeoffs, 9 being\r
+ slowest. If not set, defaults to core.compression. If that is\r
+ not set, defaults to 0 (best speed).\r
</p>\r
-<p>To let git use the new loose object format, you have to\r
-set core.legacyheaders to false.</p>\r
</dd>\r
<dt>\r
core.packedGitWindowSize\r
</p>\r
</dd>\r
<dt>\r
+gc.aggressiveWindow\r
+</dt>\r
+<dd>\r
+<p>\r
+ The window size parameter used in the delta compression\r
+ algorithm used by <em>git gc --aggressive</em>. This defaults\r
+ to 10.\r
+</p>\r
+</dd>\r
+<dt>\r
gc.packrefs\r
</dt>\r
<dd>\r
</p>\r
</dd>\r
<dt>\r
+pack.compression\r
+</dt>\r
+<dd>\r
+<p>\r
+ An integer -1..9, indicating the compression level for objects\r
+ in a pack file. -1 is the zlib default. 0 means no\r
+ compression, and 1..9 are various speed/size tradeoffs, 9 being\r
+ slowest. If not set, defaults to core.compression. If that is\r
+ not set, defaults to -1.\r
+</p>\r
+</dd>\r
+<dt>\r
pull.octopus\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 09-May-2007 07:15:31 UTC\r
+Last updated 20-May-2007 19:11:25 UTC\r
</div>\r
</div>\r
</body>\r
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-gc</em> [--prune]</p>\r
+<p><em>git-gc</em> [--prune] [--aggressive]</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
in a cron script).\r
</p>\r
</dd>\r
+<dt>\r
+--aggressive\r
+</dt>\r
+<dd>\r
+<p>\r
+ Usually <em>git-gc</em> runs very quickly while providing good disk\r
+ space utilization and performance. This option will cause\r
+ git-gc to more aggressive optimize the repository at the expense\r
+ of taking much more time. The effects of this optimization are\r
+ persistent, so this option only needs to be sporadically; every\r
+ few hundred changesets or so.\r
+</p>\r
+</dd>\r
</dl>\r
</div>\r
<h2>Configuration</h2>\r
<tt>git gc</tt> runs <tt>git-pack-refs</tt>. Without the configuration, <tt>git-pack-refs</tt>\r
is not run in bare repositories by default, to allow older dumb-transport\r
clients fetch from the repository, but this will change in the future.</p>\r
+<p>The optional configuration variable <em>gc.aggressiveWindow</em> controls how\r
+much time is spent optimizing the delta compression of the objects in\r
+the repository when the --aggressive option is specified. The larger\r
+the value, the more time is spent optimizing the delta compression. See\r
+the documentation for the --window' option in <a href="git-repack.html">git-repack(1)</a> for\r
+more details. This defaults to 10.</p>\r
</div>\r
<h2>See Also</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Apr-2007 18:33:44 UTC\r
+Last updated 20-May-2007 19:11:25 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-gc' [--prune]
+'git-gc' [--prune] [--aggressive]
DESCRIPTION
-----------
repository at the same time (e.g. never use this option
in a cron script).
+--aggressive::
+ Usually 'git-gc' runs very quickly while providing good disk
+ space utilization and performance. This option will cause
+ git-gc to more aggressive optimize the repository at the expense
+ of taking much more time. The effects of this optimization are
+ persistent, so this option only needs to be sporadically; every
+ few hundred changesets or so.
Configuration
-------------
is not run in bare repositories by default, to allow older dumb-transport
clients fetch from the repository, but this will change in the future.
+The optional configuration variable 'gc.aggressiveWindow' controls how
+much time is spent optimizing the delta compression of the objects in
+the repository when the --aggressive option is specified. The larger
+the value, the more time is spent optimizing the delta compression. See
+the documentation for the --window' option in gitlink:git-repack[1] for
+more details. This defaults to 10.
+
See Also
--------
gitlink:git-prune[1]
</p>\r
</dd>\r
<dt>\r
+--no-reuse-object\r
+</dt>\r
+<dd>\r
+<p>\r
+ This flag tells the command not to reuse existing object data at all,\r
+ including non deltified object, forcing recompression of everything.\r
+ This implies --no-reuse-delta. Useful only in the obscure case where\r
+ wholesale enforcement of a different compression level on the\r
+ packed data is desired.\r
+</p>\r
+</dd>\r
+<dt>\r
+--compression=[N]\r
+</dt>\r
+<dd>\r
+<p>\r
+ Specifies compression level for newly-compressed data in the\r
+ generated pack. If not specified, pack compression level is\r
+ determined first by pack.compression, then by core.compression,\r
+ and defaults to -1, the zlib default, if neither is set.\r
+ Data copied from loose objects will be recompressed\r
+ if core.legacyheaders was true when they were created or if\r
+ the loose compression level (see core.loosecompression and\r
+ core.compression) is now a different value than the pack\r
+ compression level. Add --no-reuse-object if you want to force\r
+ a uniform compression level on all data no matter the source.\r
+</p>\r
+</dd>\r
+<dt>\r
--delta-base-offset\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 09-May-2007 07:15:31 UTC\r
+Last updated 20-May-2007 19:11:26 UTC\r
</div>\r
</div>\r
</body>\r
This flag tells the command not to reuse existing deltas
but compute them from scratch.
+--no-reuse-object::
+ This flag tells the command not to reuse existing object data at all,
+ including non deltified object, forcing recompression of everything.
+ This implies --no-reuse-delta. Useful only in the obscure case where
+ wholesale enforcement of a different compression level on the
+ packed data is desired.
+
+--compression=[N]::
+ Specifies compression level for newly-compressed data in the
+ generated pack. If not specified, pack compression level is
+ determined first by pack.compression, then by core.compression,
+ and defaults to -1, the zlib default, if neither is set.
+ Data copied from loose objects will be recompressed
+ if core.legacyheaders was true when they were created or if
+ the loose compression level (see core.loosecompression and
+ core.compression) is now a different value than the pack
+ compression level. Add --no-reuse-object if you want to force
+ a uniform compression level on all data no matter the source.
+
--delta-base-offset::
A packed archive can express base object of a delta as
either 20-byte object name or as an offset in the
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-update-ref</em> [-m <reason>] (-d <ref> <oldvalue> | <ref> <newvalue> [<oldvalue>])</p>\r
+<p><em>git-update-ref</em> [-m <reason>] (-d <ref> <oldvalue> | [--no-deref] <ref> <newvalue> [<oldvalue>])</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
them and update them as a regular file (i.e. it will allow the\r
filesystem to follow them, but will overwrite such a symlink to\r
somewhere else with a regular filename).</p>\r
+<p>If --no-deref is given, <ref> itself is overwritten, rather than\r
+the result of following the symbolic pointers.</p>\r
<p>In general, using</p>\r
<div class="literalblock">\r
<div class="content">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Apr-2007 18:34:32 UTC\r
+Last updated 20-May-2007 19:11:27 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-update-ref' [-m <reason>] (-d <ref> <oldvalue> | <ref> <newvalue> [<oldvalue>])
+'git-update-ref' [-m <reason>] (-d <ref> <oldvalue> | [--no-deref] <ref> <newvalue> [<oldvalue>])
DESCRIPTION
-----------
filesystem to follow them, but will overwrite such a symlink to
somewhere else with a regular filename).
+If --no-deref is given, <ref> itself is overwritten, rather than
+the result of following the symbolic pointers.
+
In general, using
git-update-ref HEAD "$head"