Autogenerated HTML docs for v1.7.11-3-g60475

1 files changed, 7 insertions, 7 deletions

diff --git a/git-filter-branch.html b/git-filter-branch.html
index a3e03e76d..821059738 100644
--- a/git-filter-branch.html
+++ b/git-filter-branch.html
@@ -616,7 +616,7 @@ be able to easily push and distribute the rewritten branch on top of the
 original branch.  Please do not use this command if you do not know the

 full implications, and avoid using it anyway, if a simple single commit

 would suffice to fix your problem.  (See the "RECOVERING FROM UPSTREAM

-REBASE" section in  for further information about

+REBASE" section in <a href="git-rebase.html">git-rebase(1)</a> for further information about

 rewriting published history.)</p></div>

 <div class="paragraph"><p>Always verify that the rewritten version is correct: The original refs,

 if different from the rewritten ones, will be stored in the namespace

@@ -652,7 +652,7 @@ multiple commits.</p></div>
         This filter may be used if you only need to modify the environment

         in which the commit will be performed.  Specifically, you might

         want to rewrite the author/committer name/email/time environment

-        variables (see  for details).  Do not forget

+        variables (see <a href="git-commit-tree.html">git-commit-tree(1)</a> for details).  Do not forget

         to re-export the variables.

 </p>

 </dd>

@@ -678,7 +678,7 @@ multiple commits.</p></div>
         tree filter but does not check out the tree, which makes it much

         faster.  Frequently used with <tt>git rm --cached

         --ignore-unmatch ...</tt>, see EXAMPLES below.  For hairy

-        cases, see .

+        cases, see <a href="git-update-index.html">git-update-index(1)</a>.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -689,7 +689,7 @@ multiple commits.</p></div>
         This is the filter for rewriting the commit&#8217;s parent list.

         It will receive the parent string on stdin and shall output

         the new parent string on stdout.  The parent string is in

-        the format described in : empty for

+        the format described in <a href="git-commit-tree.html">git-commit-tree(1)</a>: empty for

         the initial commit, "-p parent" for a normal commit and

         "-p parent1 -p parent2 -p parent3 &#8230;" for a merge commit.

 </p>

@@ -826,7 +826,7 @@ to other tags will be rewritten to point to the underlying commit.</p></div>
 </dd>

 </dl></div>

 <h3 id="Remap_to_ancestor">Remap to ancestor</h3><div style="clear:left"></div>

-<div class="paragraph"><p>By using  arguments, e.g., path limiters, you can limit the

+<div class="paragraph"><p>By using <a href="rev-list.html">rev-list(1)</a> arguments, e.g., path limiters, you can limit the

 set of revisions which get rewritten. However, positive refs on the command

 line are distinguished: we don&#8217;t let them be excluded by such limiters. For

 this purpose, they are instead rewritten to point at the nearest ancestor that

@@ -997,7 +997,7 @@ to clone, that keeps your original intact.</p></div>
 <li>

 <p>

 Clone it with <tt>git clone file:///path/to/repo</tt>.  The clone

-  will not have the removed objects.  See .  (Note

+  will not have the removed objects.  See <a href="git-clone.html">git-clone(1)</a>.  (Note

   that cloning with a plain path just hardlinks everything!)

 </p>

 </li>

@@ -1030,7 +1030,7 @@ Garbage collect all unreferenced objects with <tt>git gc --prune=now</tt>
 </div>

 <h2 id="_git">GIT</h2>

 <div class="sectionbody">

-<div class="paragraph"><p>Part of the  suite</p></div>

+<div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>

 </div>

 </div>

 <div id="footnotes"><hr /></div>