Autogenerated HTML docs for v1.7.11-rc2-2-g02101

1 files changed, 15 insertions, 15 deletions

diff --git a/git-format-patch.html b/git-format-patch.html
index 9979ab872..ec9db96e6 100644
--- a/git-format-patch.html
+++ b/git-format-patch.html
@@ -618,7 +618,7 @@ A single commit, <since>, specifies that the commits leading
 <li>

 <p>

 Generic &lt;revision range&gt; expression (see "SPECIFYING

-   REVISIONS" section in <a href="gitrevisions.html">gitrevisions(7)</a>) means the

+   REVISIONS" section in ) means the

    commits in the specified range.

 </p>

 </li>

@@ -749,7 +749,7 @@ reference.</p></div>
         sub-directory. The behavior of <tt>--dirstat</tt> can be customized by

         passing it a comma separated list of parameters.

         The defaults are controlled by the <tt>diff.dirstat</tt> configuration

-        variable (see <a href="git-config.html">git-config(1)</a>).

+        variable (see ).

         The following parameters are available:

 </p>

 <div class="dlist"><dl>

@@ -1048,8 +1048,8 @@ of a delete/create pair.</p></div>
 <dd>

 <p>

         Allow an external diff helper to be executed. If you set an

-        external diff driver with <a href="gitattributes.html">gitattributes(5)</a>, you need

-        to use this option with <a href="git-log.html">git-log(1)</a> and friends.

+        external diff driver with , you need

+        to use this option with  and friends.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1069,12 +1069,12 @@ of a delete/create pair.</p></div>
 <dd>

 <p>

         Allow (or disallow) external text conversion filters to be run

-        when comparing binary files. See <a href="gitattributes.html">gitattributes(5)</a> for

+        when comparing binary files. See  for

         details. Because textconv filters are typically a one-way

         conversion, the resulting diff is suitable for human

         consumption, but cannot be applied. For this reason, textconv

-        filters are enabled by default only for <a href="git-diff.html">git-diff(1)</a> and

-        <a href="git-log.html">git-log(1)</a>, but not for <a href="git-format-patch.html">git-format-patch(1)</a> or

+        filters are enabled by default only for  and

+        , but not for  or

         diff plumbing commands.

 </p>

 </dd>

@@ -1088,7 +1088,7 @@ of a delete/create pair.</p></div>
         Using "none" will consider the submodule modified when it either contains

         untracked or modified files or its HEAD differs from the commit recorded

         in the superproject and can be used to override any settings of the

-        <em>ignore</em> option in <a href="git-config.html">git-config(1)</a> or <a href="gitmodules.html">gitmodules(5)</a>. When

+        <em>ignore</em> option in  or . When

         "untracked" is used submodules are not considered dirty when they only

         contain untracked content (but they are still scanned for modified

         content). Using "dirty" ignores all changes to the work tree of submodules,

@@ -1122,7 +1122,7 @@ of a delete/create pair.</p></div>
 </dd>

 </dl></div>

 <div class="paragraph"><p>For more detailed explanation on these common options, see also

-<a href="gitdiffcore.html">gitdiffcore(7)</a>.</p></div>

+.</p></div>

 <div class="dlist"><dl>

 <dt class="hdlist1">

 -&lt;n&gt;

@@ -1451,7 +1451,7 @@ timely commentary that should not go in the changelog after the three
 dashes, and then sent as a message whose body, in our example, starts

 with "arch/arm config files were&#8230;".  On the receiving end, readers

 can save interesting patches in a UNIX mailbox and apply them with

-<a href="git-am.html">git-am(1)</a>.</p></div>

+.</p></div>

 <div class="paragraph"><p>When a patch is part of an ongoing discussion, the patch generated by

 <em>git format-patch</em> can be tweaked to take advantage of the <em>git am

 --scissors</em> feature.  After your response to the discussion comes a

@@ -1526,7 +1526,7 @@ $ git am a.patch</tt></pre>
 <p>

 The patch itself does not apply cleanly.  That is <em>bad</em> but

   does not have much to do with your MUA.  You might want to rebase

-  the patch with <a href="git-rebase.html">git-rebase(1)</a> before regenerating it in

+  the patch with  before regenerating it in

   this case.

 </p>

 </li>

@@ -1562,9 +1562,9 @@ use "git send-email" and send your patches through the GMail SMTP server, or
 use any IMAP email client to connect to the google IMAP server and forward

 the emails through that.</p></div>

 <div class="paragraph"><p>For hints on using <em>git send-email</em> to send your patches through the

-GMail SMTP server, see the EXAMPLE section of <a href="git-send-email.html">git-send-email(1)</a>.</p></div>

+GMail SMTP server, see the EXAMPLE section of .</p></div>

 <div class="paragraph"><p>For hints on submission using the IMAP interface, see the EXAMPLE

-section of <a href="git-imap-send.html">git-imap-send(1)</a>.</p></div>

+section of .</p></div>

 <h3 id="_thunderbird">Thunderbird</h3><div style="clear:left"></div>

 <div class="paragraph"><p>By default, Thunderbird will both wrap emails as well as flag

 them as being <em>format=flowed</em>, both of which will make the

@@ -1759,11 +1759,11 @@ as e-mailable patches:
 </div>

 <h2 id="_see_also">SEE ALSO</h2>

 <div class="sectionbody">

-<div class="paragraph"><p><a href="git-am.html">git-am(1)</a>, <a href="git-send-email.html">git-send-email(1)</a></p></div>

+<div class="paragraph"><p>, </p></div>

 </div>

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

 <div class="sectionbody">

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

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

 </div>

 </div>

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