at some stage, and setting this to `false` will continue to
prevent `git pack-refs` from being run from `git gc`.
+gc.pruneexpire::
+ When `git gc` is run, it will call `prune --expire 2.weeks.ago`.
+ Override the grace period with this config variable.
+
gc.reflogexpire::
`git reflog expire` removes reflog entries older than
this time; defaults to 90 days.
whenever the corresponding pack is larger than 2 GB. Otherwise
the default is 1.
-pack.packSizeLimit:
+pack.packSizeLimit::
The default maximum size of a pack. This setting only affects
packing to a file, i.e. the git:// protocol is unaffected. It
can be overridden by the `\--max-pack-size` option of
</p>\r
</dd>\r
<dt>\r
+gc.pruneexpire\r
+</dt>\r
+<dd>\r
+<p>\r
+ When <tt>git gc</tt> is run, it will call <tt>prune --expire 2.weeks.ago</tt>.\r
+ Override the grace period with this config variable.\r
+</p>\r
+</dd>\r
+<dt>\r
gc.reflogexpire\r
</dt>\r
<dd>\r
the default is 1.\r
</p>\r
</dd>\r
-</dl>\r
-<p>pack.packSizeLimit:\r
+<dt>\r
+pack.packSizeLimit\r
+</dt>\r
+<dd>\r
+<p>\r
The default maximum size of a pack. This setting only affects\r
packing to a file, i.e. the git:// protocol is unaffected. It\r
can be overridden by the <tt>--max-pack-size</tt> option of\r
- <a href="git-repack.html">git-repack(1)</a>.</p>\r
-<dl>\r
+ <a href="git-repack.html">git-repack(1)</a>.\r
+</p>\r
+</dd>\r
<dt>\r
pull.octopus\r
</dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 08-Mar-2008 09:29:57 UTC\r
+Last updated 13-Mar-2008 07:53:35 UTC\r
</div>\r
</div>\r
</body>\r
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-gc</em> [--prune] [--aggressive] [--auto] [--quiet]</p>\r
+<p><em>git-gc</em> [--aggressive] [--auto] [--quiet]</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
<div class="sectionbody">\r
<dl>\r
<dt>\r
---prune\r
-</dt>\r
-<dd>\r
-<p>\r
- Usually <tt>git-gc</tt> packs refs, expires old reflog entries,\r
- packs loose objects,\r
- and removes old <em>rerere</em> records. Removal\r
- of unreferenced loose objects is an unsafe operation\r
- while other git operations are in progress, so it is not\r
- done by default. Pass this option if you want it, and only\r
- when you know nobody else is creating new objects in the\r
- repository at the same time (e.g. never use this option\r
- in a cron script).\r
-</p>\r
-</dd>\r
-<dt>\r
--aggressive\r
</dt>\r
<dd>\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
+<p>The optional configuration variable <em>gc.pruneExpire</em> controls how old\r
+the unreferenced loose objects have to be before they are pruned. The\r
+default is "2 weeks ago".</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 01-Mar-2008 18:41:39 UTC\r
+Last updated 13-Mar-2008 07:53:35 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-gc' [--prune] [--aggressive] [--auto] [--quiet]
+'git-gc' [--aggressive] [--auto] [--quiet]
DESCRIPTION
-----------
OPTIONS
-------
---prune::
- Usually `git-gc` packs refs, expires old reflog entries,
- packs loose objects,
- and removes old 'rerere' records. Removal
- of unreferenced loose objects is an unsafe operation
- while other git operations are in progress, so it is not
- done by default. Pass this option if you want it, and only
- when you know nobody else is creating new objects in the
- 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
the documentation for the --window' option in linkgit:git-repack[1] for
more details. This defaults to 10.
+The optional configuration variable 'gc.pruneExpire' controls how old
+the unreferenced loose objects have to be before they are pruned. The
+default is "2 weeks ago".
+
See Also
--------
linkgit:git-prune[1]