Autogenerated HTML docs for v1.8.1.2-545-g2f19ad

1 files changed, 25 insertions, 25 deletions

diff --git a/git-remote-helpers.html b/git-remote-helpers.html
index 2c8c15bfd..0bbb08c44 100644
--- a/git-remote-helpers.html
+++ b/git-remote-helpers.html
@@ -755,16 +755,16 @@ git-remote-helpers(1) Manual Page
 <h2 id="_description">DESCRIPTION</h2>

 <div class="sectionbody">

 <div class="paragraph"><p>Remote helper programs are normally not used directly by end users,

-but they are invoked by git when it needs to interact with remote

-repositories git does not support natively.  A given helper will

-implement a subset of the capabilities documented here. When git

+but they are invoked by Git when it needs to interact with remote

+repositories Git does not support natively.  A given helper will

+implement a subset of the capabilities documented here. When Git

 needs to interact with a repository using a remote helper, it spawns

 the helper as an independent process, sends commands to the helper&#8217;s

 standard input, and expects results from the helper&#8217;s standard

 output. Because a remote helper runs as an independent process from

-git, there is no need to re-link git to add a new helper, nor any

-need to link the helper with the implementation of git.</p></div>

-<div class="paragraph"><p>Every helper must support the "capabilities" command, which git

+Git, there is no need to re-link Git to add a new helper, nor any

+need to link the helper with the implementation of Git.</p></div>

+<div class="paragraph"><p>Every helper must support the "capabilities" command, which Git

 uses to determine what other commands the helper will accept.  Those

 other commands can be used to discover and update remote refs,

 transport objects between the object database and the remote repository,

@@ -779,27 +779,27 @@ transport protocols, such as <em>git-remote-http</em>, <em>git-remote-https</em>
 <h2 id="_invocation">INVOCATION</h2>

 <div class="sectionbody">

 <div class="paragraph"><p>Remote helper programs are invoked with one or (optionally) two

-arguments. The first argument specifies a remote repository as in git;

+arguments. The first argument specifies a remote repository as in Git;

 it is either the name of a configured remote or a URL. The second

 argument specifies a URL; it is usually of the form

 <em>&lt;transport&gt;://&lt;address&gt;</em>, but any arbitrary string is possible.

 The <em>GIT_DIR</em> environment variable is set up for the remote helper

 and can be used to determine where to store additional data or from

-which directory to invoke auxiliary git commands.</p></div>

-<div class="paragraph"><p>When git encounters a URL of the form <em>&lt;transport&gt;://&lt;address&gt;</em>, where

+which directory to invoke auxiliary Git commands.</p></div>

+<div class="paragraph"><p>When Git encounters a URL of the form <em>&lt;transport&gt;://&lt;address&gt;</em>, where

 <em>&lt;transport&gt;</em> is a protocol that it cannot handle natively, it

 automatically invokes <em>git remote-&lt;transport&gt;</em> with the full URL as

 the second argument. If such a URL is encountered directly on the

 command line, the first argument is the same as the second, and if it

 is encountered in a configured remote, the first argument is the name

 of that remote.</p></div>

-<div class="paragraph"><p>A URL of the form <em>&lt;transport&gt;::&lt;address&gt;</em> explicitly instructs git to

+<div class="paragraph"><p>A URL of the form <em>&lt;transport&gt;::&lt;address&gt;</em> explicitly instructs Git to

 invoke <em>git remote-&lt;transport&gt;</em> with <em>&lt;address&gt;</em> as the second

 argument. If such a URL is encountered directly on the command line,

 the first argument is <em>&lt;address&gt;</em>, and if it is encountered in a

 configured remote, the first argument is the name of that remote.</p></div>

 <div class="paragraph"><p>Additionally, when a configured remote has <em>remote.&lt;name&gt;.vcs</em> set to

-<em>&lt;transport&gt;</em>, git explicitly invokes <em>git remote-&lt;transport&gt;</em> with

+<em>&lt;transport&gt;</em>, Git explicitly invokes <em>git remote-&lt;transport&gt;</em> with

 <em>&lt;name&gt;</em> as the first argument. If set, the second argument is

 <em>remote.&lt;name&gt;.url</em>; otherwise, the second argument is omitted.</p></div>

 </div>

@@ -820,7 +820,7 @@ protocol), while in others it indicates the end of input.</p></div>
 <div class="sect2">

 <h3 id="_capabilities">Capabilities</h3>

 <div class="paragraph"><p>Each remote helper is expected to support only a subset of commands.

-The operations a helper supports are declared to git in the response

+The operations a helper supports are declared to Git in the response

 to the <code>capabilities</code> command (see COMMANDS, below).</p></div>

 <div class="paragraph"><p>In the following, we list all defined capabilities and for

 each we list which commands a helper with that capability

@@ -861,10 +861,10 @@ must provide.</p></div>
 <div class="paragraph"><p>Supported commands: <em>list for-push</em>, <em>export</em>.</p></div>

 </dd>

 </dl></div>

-<div class="paragraph"><p>If a helper advertises <em>connect</em>, git will use it if possible and

+<div class="paragraph"><p>If a helper advertises <em>connect</em>, Git will use it if possible and

 fall back to another capability if the helper requests so when

 connecting (see the <em>connect</em> command under COMMANDS).

-When choosing between <em>push</em> and <em>export</em>, git prefers <em>push</em>.

+When choosing between <em>push</em> and <em>export</em>, Git prefers <em>push</em>.

 Other frontends may have some other order of preference.</p></div>

 </div>

 <div class="sect3">

@@ -877,7 +877,7 @@ Other frontends may have some other order of preference.</p></div>
 <p>

         Can try to connect to <em>git upload-pack</em> (for fetching),

         <em>git receive-pack</em>, etc for communication using the

-        git&#8217;s native packfile protocol. This

+        Git&#8217;s native packfile protocol. This

         requires a bidirectional, full-duplex connection.

 </p>

 <div class="paragraph"><p>Supported commands: <em>connect</em>.</p></div>

@@ -903,10 +903,10 @@ Other frontends may have some other order of preference.</p></div>
 <div class="paragraph"><p>Supported commands: <em>list</em>, <em>import</em>.</p></div>

 </dd>

 </dl></div>

-<div class="paragraph"><p>If a helper advertises <em>connect</em>, git will use it if possible and

+<div class="paragraph"><p>If a helper advertises <em>connect</em>, Git will use it if possible and

 fall back to another capability if the helper requests so when

 connecting (see the <em>connect</em> command under COMMANDS).

-When choosing between <em>fetch</em> and <em>import</em>, git prefers <em>fetch</em>.

+When choosing between <em>fetch</em> and <em>import</em>, Git prefers <em>fetch</em>.

 Other frontends may have some other order of preference.</p></div>

 </div>

 <div class="sect3">

@@ -955,10 +955,10 @@ there is an implied <code>refspec *:*</code>.</p></div>
         to retrieve information about blobs and trees that already exist in

         fast-import&#8217;s memory. This requires a channel from fast-import to the

         remote-helper.

-        If it is advertised in addition to "import", git establishes a pipe from

+        If it is advertised in addition to "import", Git establishes a pipe from

         fast-import to the remote-helper&#8217;s stdin.

-        It follows that git and fast-import are both connected to the

-        remote-helper&#8217;s stdin. Because git can send multiple commands to

+        It follows that Git and fast-import are both connected to the

+        remote-helper&#8217;s stdin. Because Git can send multiple commands to

         the remote-helper it is required that helpers that use <em>bidi-import</em>

         buffer all <em>import</em> commands of a batch before sending data to fast-import.

         This is to prevent mixing commands and fast-import responses on the

@@ -970,7 +970,7 @@ there is an implied <code>refspec *:*</code>.</p></div>
 </dt>

 <dd>

 <p>

-        This modifies the <em>export</em> capability, instructing git to dump the

+        This modifies the <em>export</em> capability, instructing Git to dump the

         internal marks table to &lt;file&gt; when complete. For details,

         read up on <em>--export-marks=&lt;file&gt;</em> in <a href="git-fast-export.html">git-fast-export(1)</a>.

 </p>

@@ -980,7 +980,7 @@ there is an implied <code>refspec *:*</code>.</p></div>
 </dt>

 <dd>

 <p>

-        This modifies the <em>export</em> capability, instructing git to load the

+        This modifies the <em>export</em> capability, instructing Git to load the

         marks specified in &lt;file&gt; before processing any input. For details,

         read up on <em>--import-marks=&lt;file&gt;</em> in <a href="git-fast-export.html">git-fast-export(1)</a>.

 </p>

@@ -1002,7 +1002,7 @@ there is an implied <code>refspec *:*</code>.</p></div>
 <p>

         Lists the capabilities of the helper, one per line, ending

         with a blank line. Each capability may be preceded with <em>*</em>,

-        which marks them mandatory for git versions using the remote

+        which marks them mandatory for Git versions using the remote

         helper to understand. Any unknown mandatory capability is a

         fatal error.

 </p>

@@ -1196,7 +1196,7 @@ attributes are defined.</p></div>
 <h2 id="_options">OPTIONS</h2>

 <div class="sectionbody">

 <div class="paragraph"><p>The following options are defined and (under suitable circumstances)

-set by git if the remote helper has the <em>option</em> capability.</p></div>

+set by Git if the remote helper has the <em>option</em> capability.</p></div>

 <div class="dlist"><dl>

 <dt class="hdlist1">

 <em>option verbosity</em> &lt;n&gt;

@@ -1278,7 +1278,7 @@ set by git if the remote helper has the <em>option</em> capability.</p></div>
 <div id="footnotes"><hr /></div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2012-12-13 12:34:41 PST

+Last updated 2013-02-05 21:07:26 PST

 </div>

 </div>

 </body>