Autogenerated HTML docs for v1.5.0-rc2-g8a816

1 files changed, 11 insertions, 2 deletions

diff --git a/git-pack-refs.html b/git-pack-refs.html
index da7856c35..04f506b2d 100644
--- a/git-pack-refs.html
+++ b/git-pack-refs.html
@@ -290,6 +290,14 @@ traditional <tt>$GIT_DIR/refs</tt> hierarchy, it is looked up in this
 file and used if found.</p>

 <p>Subsequent updates to branches always creates new file under

 <tt>$GIT_DIR/refs</tt> hierarchy.</p>

+<p>A recommended practice to deal with a repository with too many

+refs is to pack its refs with <tt>--all --prune</tt> once, and

+occasionally run <tt>git-pack-refs --prune</tt>.  Tags are by

+definition stationary and are not expected to change.  Branch

+heads will be packed with the initial <tt>pack-refs --all</tt>, but

+only the currently active branch heads will become unpacked,

+and next <tt>pack-refs</tt> (without <tt>--all</tt>) will leave them

+unpacked.</p>

 </div>

 <h2>OPTIONS</h2>

 <div class="sectionbody">

@@ -299,7 +307,8 @@ file and used if found.</p>
 </dt>

 <dd>

 <p>

-The command by default packs all tags and leaves branch tips

+The command by default packs all tags and refs that are already

+packed, and leaves other refs

 alone.  This is because branches are expected to be actively

 developed and packing their tips does not help performance.

 This option causes branch tips to be packed as well.  Useful for

@@ -327,7 +336,7 @@ hierarchy after packing them.  This option tells it not to.
 </div>

 <div id="footer">

 <div id="footer-text">

-Last updated 09-Jan-2007 11:13:40 UTC

+Last updated 26-Jan-2007 09:44:40 UTC

 </div>

 </div>

 </body>