summaryrefslogtreecommitdiffstats
path: root/git.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-02-05 21:13:21 -0800
committerJunio C Hamano <gitster@pobox.com>2013-02-05 21:13:21 -0800
commit076ffcc834f02a4f11d7f4fe8825be3b065020ff (patch)
tree6f5fa28df80c60c9b0a1dfab028d3db33ae22fa0 /git.html
parent3f2ed6f9b744f05cf2ad32b0c0c80aa149d9fdcb (diff)
downloadgit-htmldocs-076ffcc834f02a4f11d7f4fe8825be3b065020ff.tar.gz
Autogenerated HTML docs for v1.8.1.2-545-g2f19ad
Diffstat (limited to 'git.html')
-rw-r--r--git.html114
1 files changed, 57 insertions, 57 deletions
diff --git a/git.html b/git.html
index b1c2ca13d..35626cb55 100644
--- a/git.html
+++ b/git.html
@@ -766,10 +766,10 @@ and full access to internals.</p></div>
commands. The <a href="user-manual.html">Git User&#8217;s Manual</a> has a more
in-depth introduction.</p></div>
<div class="paragraph"><p>After you mastered the basic concepts, you can come back to this
-page to learn what commands git offers. You can learn more about
-individual git commands with "git help command". <a href="gitcli.html">gitcli(7)</a>
+page to learn what commands Git offers. You can learn more about
+individual Git commands with "git help command". <a href="gitcli.html">gitcli(7)</a>
manual page gives you an overview of the command line command syntax.</p></div>
-<div class="paragraph"><p>Formatted and hyperlinked version of the latest git documentation
+<div class="paragraph"><p>Formatted and hyperlinked version of the latest Git documentation
can be viewed at <code>http://git-htmldocs.googlecode.com/git/git.html</code>.</p></div>
</div>
</div>
@@ -782,7 +782,7 @@ can be viewed at <code>http://git-htmldocs.googlecode.com/git/git.html</code>.</
</dt>
<dd>
<p>
- Prints the git suite version that the <em>git</em> program came from.
+ Prints the Git suite version that the <em>git</em> program came from.
</p>
</dd>
<dt class="hdlist1">
@@ -792,7 +792,7 @@ can be viewed at <code>http://git-htmldocs.googlecode.com/git/git.html</code>.</
<p>
Prints the synopsis and a list of the most commonly used
commands. If the option <em>--all</em> or <em>-a</em> is given then all
- available commands are printed. If a git command is named this
+ available commands are printed. If a Git command is named this
option will bring up the manual page for that command.
</p>
<div class="paragraph"><p>Other options are available to control how the manual page is
@@ -816,7 +816,7 @@ help ...</code>.</p></div>
</dt>
<dd>
<p>
- Path to wherever your core git programs are installed.
+ Path to wherever your core Git programs are installed.
This can also be controlled by setting the GIT_EXEC_PATH
environment variable. If no path is given, <em>git</em> will print
the current setting and then exit.
@@ -827,7 +827,7 @@ help ...</code>.</p></div>
</dt>
<dd>
<p>
- Print the path, without trailing slash, where git&#8217;s HTML
+ Print the path, without trailing slash, where Git&#8217;s HTML
documentation is installed and exit.
</p>
</dd>
@@ -837,7 +837,7 @@ help ...</code>.</p></div>
<dd>
<p>
Print the manpath (see <code>man(1)</code>) for the man pages for
- this version of git and exit.
+ this version of Git and exit.
</p>
</dd>
<dt class="hdlist1">
@@ -846,7 +846,7 @@ help ...</code>.</p></div>
<dd>
<p>
Print the path where the Info files documenting this
- version of git are installed and exit.
+ version of Git are installed and exit.
</p>
</dd>
<dt class="hdlist1">
@@ -868,7 +868,7 @@ help ...</code>.</p></div>
</dt>
<dd>
<p>
- Do not pipe git output into a pager.
+ Do not pipe Git output into a pager.
</p>
</dd>
<dt class="hdlist1">
@@ -899,7 +899,7 @@ help ...</code>.</p></div>
</dt>
<dd>
<p>
- Set the git namespace. See <a href="gitnamespaces.html">gitnamespaces(7)</a> for more
+ Set the Git namespace. See <a href="gitnamespaces.html">gitnamespaces(7)</a> for more
details. Equivalent to setting the <code>GIT_NAMESPACE</code> environment
variable.
</p>
@@ -919,7 +919,7 @@ help ...</code>.</p></div>
</dt>
<dd>
<p>
- Do not use replacement refs to replace git objects. See
+ Do not use replacement refs to replace Git objects. See
<a href="git-replace.html">git-replace(1)</a> for more information.
</p>
</dd>
@@ -939,7 +939,7 @@ help ...</code>.</p></div>
<div class="sect1">
<h2 id="_git_commands">GIT COMMANDS</h2>
<div class="sectionbody">
-<div class="paragraph"><p>We divide git into high level ("porcelain") commands and low level
+<div class="paragraph"><p>We divide Git into high level ("porcelain") commands and low level
("plumbing") commands.</p></div>
</div>
</div>
@@ -1108,7 +1108,7 @@ ancillary user utilities.</p></div>
</dt>
<dd>
<p>
- Create an empty git repository or reinitialize an existing one.
+ Create an empty Git repository or reinitialize an existing one.
</p>
</dd>
<dt class="hdlist1">
@@ -1244,7 +1244,7 @@ ancillary user utilities.</p></div>
</dt>
<dd>
<p>
- The git repository browser.
+ The Git repository browser.
</p>
</dd>
</dl></div>
@@ -1429,7 +1429,7 @@ ancillary user utilities.</p></div>
</dt>
<dd>
<p>
- display help information about git.
+ Display help information about Git.
</p>
</dd>
<dt class="hdlist1">
@@ -1508,7 +1508,7 @@ people via patch over e-mail.</p></div>
</dt>
<dd>
<p>
- Import an Arch repository into git.
+ Import an Arch repository into Git.
</p>
</dd>
<dt class="hdlist1">
@@ -1532,7 +1532,7 @@ people via patch over e-mail.</p></div>
</dt>
<dd>
<p>
- A CVS server emulator for git.
+ A CVS server emulator for Git.
</p>
</dd>
<dt class="hdlist1">
@@ -1580,7 +1580,7 @@ people via patch over e-mail.</p></div>
</dt>
<dd>
<p>
- Bidirectional operation between a Subversion repository and git.
+ Bidirectional operation between a Subversion repository and Git.
</p>
</dd>
</dl></div>
@@ -1590,7 +1590,7 @@ people via patch over e-mail.</p></div>
<div class="sect1">
<h2 id="_low_level_commands_plumbing">Low-level commands (plumbing)</h2>
<div class="sectionbody">
-<div class="paragraph"><p>Although git includes its
+<div class="paragraph"><p>Although Git includes its
own porcelain layer, its low-level commands are sufficient to support
development of alternative porcelains. Developers of such porcelains
might start by reading about <a href="git-update-index.html">git-update-index(1)</a> and
@@ -1883,7 +1883,7 @@ repositories.</p></div>
</dt>
<dd>
<p>
- Show a git logical variable.
+ Show a Git logical variable.
</p>
</dd>
<dt class="hdlist1">
@@ -1891,7 +1891,7 @@ repositories.</p></div>
</dt>
<dd>
<p>
- Validate packed git archive files.
+ Validate packed Git archive files.
</p>
</dd>
</dl></div>
@@ -1906,7 +1906,7 @@ the working tree.</p></div>
</dt>
<dd>
<p>
- A really simple server for git repositories.
+ A really simple server for Git repositories.
</p>
</dd>
<dt class="hdlist1">
@@ -1930,7 +1930,7 @@ the working tree.</p></div>
</dt>
<dd>
<p>
- Push objects over git protocol to another repository.
+ Push objects over Git protocol to another repository.
</p>
</dd>
<dt class="hdlist1">
@@ -1950,7 +1950,7 @@ typically do not use them directly.</p></div>
</dt>
<dd>
<p>
- Download from a remote git repository via HTTP.
+ Download from a remote Git repository via HTTP.
</p>
</dd>
<dt class="hdlist1">
@@ -2125,7 +2125,7 @@ users typically do not use them directly.</p></div>
</dt>
<dd>
<p>
- Common git shell script setup code.
+ Common Git shell script setup code.
</p>
</dd>
<dt class="hdlist1">
@@ -2250,7 +2250,7 @@ list.</p></div>
<div class="sect1">
<h2 id="_symbolic_identifiers">Symbolic Identifiers</h2>
<div class="sectionbody">
-<div class="paragraph"><p>Any git command accepting any &lt;object&gt; can also use the following
+<div class="paragraph"><p>Any Git command accepting any &lt;object&gt; can also use the following
symbolic notation:</p></div>
<div class="dlist"><dl>
<dt class="hdlist1">
@@ -2302,12 +2302,12 @@ HEAD
<div class="sect1">
<h2 id="_environment_variables">Environment Variables</h2>
<div class="sectionbody">
-<div class="paragraph"><p>Various git commands use the following environment variables:</p></div>
+<div class="paragraph"><p>Various Git commands use the following environment variables:</p></div>
<div class="sect2">
-<h3 id="_the_git_repository">The git Repository</h3>
-<div class="paragraph"><p>These environment variables apply to <em>all</em> core git commands. Nb: it
+<h3 id="_the_git_repository">The Git Repository</h3>
+<div class="paragraph"><p>These environment variables apply to <em>all</em> core Git commands. Nb: it
is worth noting that they may be used/overridden by SCMS sitting above
-git so take care if using Cogito etc.</p></div>
+Git so take care if using Cogito etc.</p></div>
<div class="dlist"><dl>
<dt class="hdlist1">
<em>GIT_INDEX_FILE</em>
@@ -2335,10 +2335,10 @@ git so take care if using Cogito etc.</p></div>
</dt>
<dd>
<p>
- Due to the immutable nature of git objects, old objects can be
+ Due to the immutable nature of Git objects, old objects can be
archived into shared, read-only directories. This variable
specifies a ":" separated (on Windows ";" separated) list
- of git object directories which can be used to search for git
+ of Git object directories which can be used to search for Git
objects. New objects will not be written to these directories.
</p>
</dd>
@@ -2370,7 +2370,7 @@ git so take care if using Cogito etc.</p></div>
</dt>
<dd>
<p>
- Set the git namespace; see <a href="gitnamespaces.html">gitnamespaces(7)</a> for details.
+ Set the Git namespace; see <a href="gitnamespaces.html">gitnamespaces(7)</a> for details.
The <em>--namespace</em> command-line option also sets this value.
</p>
</dd>
@@ -2380,7 +2380,7 @@ git so take care if using Cogito etc.</p></div>
<dd>
<p>
This should be a colon-separated list of absolute paths.
- If set, it is a list of directories that git should not chdir
+ If set, it is a list of directories that Git should not chdir
up into while looking for a repository directory.
It will not exclude the current working directory or
a GIT_DIR set on the command line or in the environment.
@@ -2393,10 +2393,10 @@ git so take care if using Cogito etc.</p></div>
<dd>
<p>
When run in a directory that does not have ".git" repository
- directory, git tries to find such a directory in the parent
+ directory, Git tries to find such a directory in the parent
directories to find the top of the working tree, but by default it
does not cross filesystem boundaries. This environment variable
- can be set to true to tell git not to stop at filesystem
+ can be set to true to tell Git not to stop at filesystem
boundaries. Like <em>GIT_CEILING_DIRECTORIES</em>, this will not affect
an explicit repository directory set via <em>GIT_DIR</em> or on the
command line.
@@ -2405,7 +2405,7 @@ git so take care if using Cogito etc.</p></div>
</dl></div>
</div>
<div class="sect2">
-<h3 id="_git_commits">git Commits</h3>
+<h3 id="_git_commits">Git Commits</h3>
<div class="dlist"><dl>
<dt class="hdlist1">
<em>GIT_AUTHOR_NAME</em>
@@ -2436,7 +2436,7 @@ git so take care if using Cogito etc.</p></div>
</dl></div>
</div>
<div class="sect2">
-<h3 id="_git_diffs">git Diffs</h3>
+<h3 id="_git_diffs">Git Diffs</h3>
<div class="dlist"><dl>
<dt class="hdlist1">
<em>GIT_DIFF_OPTS</em>
@@ -2446,7 +2446,7 @@ git so take care if using Cogito etc.</p></div>
Only valid setting is "--unified=??" or "-u??" to set the
number of context lines shown when a unified diff is created.
This takes precedence over any "-U" or "--unified" option
- value passed on the git diff command line.
+ value passed on the Git diff command line.
</p>
</dd>
<dt class="hdlist1">
@@ -2518,7 +2518,7 @@ parameter, &lt;path&gt;.</p></div>
<dd>
<p>
This environment variable overrides <code>$PAGER</code>. If it is set
- to an empty string or to the value "cat", git will not launch
+ to an empty string or to the value "cat", Git will not launch
a pager. See also the <code>core.pager</code> option in
<a href="git-config.html">git-config(1)</a>.
</p>
@@ -2529,7 +2529,7 @@ parameter, &lt;path&gt;.</p></div>
<dd>
<p>
This environment variable overrides <code>$EDITOR</code> and <code>$VISUAL</code>.
- It is used by several git commands when, on interactive mode,
+ It is used by several Git commands when, on interactive mode,
an editor is to be launched. See also <a href="git-var.html">git-var(1)</a>
and the <code>core.editor</code> option in <a href="git-config.html">git-config(1)</a>.
</p>
@@ -2558,7 +2558,7 @@ for further details.</p></div>
</dt>
<dd>
<p>
- If this environment variable is set, then git commands which need to
+ If this environment variable is set, then Git commands which need to
acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
will call this program with a suitable prompt as command line argument
and read the password from its STDOUT. See also the <em>core.askpass</em>
@@ -2589,7 +2589,7 @@ for further details.</p></div>
after each commit-oriented record have been flushed. If this
variable is set to "0", the output of these commands will be done
using completely buffered I/O. If this environment variable is
- not set, git will choose buffered or record-oriented flushing
+ not set, Git will choose buffered or record-oriented flushing
based on whether stdout appears to be redirected to a file or not.
</p>
</dd>
@@ -2599,15 +2599,15 @@ for further details.</p></div>
<dd>
<p>
If this variable is set to "1", "2" or "true" (comparison
- is case insensitive), git will print <code>trace:</code> messages on
+ is case insensitive), Git will print <code>trace:</code> messages on
stderr telling about alias expansion, built-in command
execution and external command execution.
If this variable is set to an integer value greater than 1
- and lower than 10 (strictly) then git will interpret this
+ and lower than 10 (strictly) then Git will interpret this
value as an open file descriptor and will try to write the
trace messages into this file descriptor.
Alternatively, if this variable is set to an absolute path
- (starting with a <em>/</em> character), git will interpret this
+ (starting with a <em>/</em> character), Git will interpret this
as a file path and will try to write the trace messages
into it.
</p>
@@ -2617,12 +2617,12 @@ GIT_LITERAL_PATHSPECS
</dt>
<dd>
<p>
- Setting this variable to <code>1</code> will cause git to treat all
+ Setting this variable to <code>1</code> will cause Git to treat all
pathspecs literally, rather than as glob patterns. For example,
running <code>GIT_LITERAL_PATHSPECS=1 git log -- '*.c'</code> will search
for commits that touch the path <code>*.c</code>, not any paths that the
glob <code>*.c</code> matches. You might want this if you are feeding
- literal paths to git (e.g., paths previously given to you by
+ literal paths to Git (e.g., paths previously given to you by
<code>git ls-tree</code>, <code>--raw</code> diff output, etc).
</p>
</dd>
@@ -2634,9 +2634,9 @@ GIT_LITERAL_PATHSPECS
<h2 id="_discussion_a_id_discussion_a">Discussion<a id="Discussion"></a></h2>
<div class="sectionbody">
<div class="paragraph"><p>More detail on the following is available from the
-<a href="user-manual.html#git-concepts">git concepts chapter of the
+<a href="user-manual.html#git-concepts">Git concepts chapter of the
user-manual</a> and <a href="gitcore-tutorial.html">gitcore-tutorial(7)</a>.</p></div>
-<div class="paragraph"><p>A git project normally consists of a working directory with a ".git"
+<div class="paragraph"><p>A Git project normally consists of a working directory with a ".git"
subdirectory at the top level. The .git directory contains, among other
things, a compressed object database representing the complete history
of the project, an "index" file which links that history to the current
@@ -2680,16 +2680,16 @@ unmerged version of a file when a merge is in progress.</p></div>
<h2 id="_further_documentation">FURTHER DOCUMENTATION</h2>
<div class="sectionbody">
<div class="paragraph"><p>See the references in the "description" section to get started
-using git. The following is probably more detail than necessary
+using Git. The following is probably more detail than necessary
for a first-time user.</p></div>
-<div class="paragraph"><p>The <a href="user-manual.html#git-concepts">git concepts chapter of the
+<div class="paragraph"><p>The <a href="user-manual.html#git-concepts">Git concepts chapter of the
user-manual</a> and <a href="gitcore-tutorial.html">gitcore-tutorial(7)</a> both provide
-introductions to the underlying git architecture.</p></div>
+introductions to the underlying Git architecture.</p></div>
<div class="paragraph"><p>See <a href="gitworkflows.html">gitworkflows(7)</a> for an overview of recommended workflows.</p></div>
<div class="paragraph"><p>See also the <a href="howto-index.html">howto</a> documents for some useful
examples.</p></div>
<div class="paragraph"><p>The internals are documented in the
-<a href="technical/api-index.html">GIT API documentation</a>.</p></div>
+<a href="technical/api-index.html">Git API documentation</a>.</p></div>
<div class="paragraph"><p>Users migrating from CVS may also want to
read <a href="gitcvs-migration.html">gitcvs-migration(7)</a>.</p></div>
</div>
@@ -2698,7 +2698,7 @@ read <a href="gitcvs-migration.html">gitcvs-migration(7)</a>.</p></div>
<h2 id="_authors">Authors</h2>
<div class="sectionbody">
<div class="paragraph"><p>Git was started by Linus Torvalds, and is currently maintained by Junio
-C Hamano. Numerous contributions have come from the git mailing list
+C Hamano. Numerous contributions have come from the Git mailing list
&lt;<a href="mailto:git@vger.kernel.org">git@vger.kernel.org</a>&gt;. <a href="http://www.ohloh.net/p/git/contributors/summary">http://www.ohloh.net/p/git/contributors/summary</a>
gives you a more complete list of contributors.</p></div>
<div class="paragraph"><p>If you have a clone of git.git itself, the
@@ -2734,7 +2734,7 @@ subscribed to the list to send a message there.</p></div>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-01-14 11:47:43 PST
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>