summaryrefslogtreecommitdiffstats
path: root/gitcli.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 /gitcli.html
parent3f2ed6f9b744f05cf2ad32b0c0c80aa149d9fdcb (diff)
downloadgit-htmldocs-076ffcc834f02a4f11d7f4fe8825be3b065020ff.tar.gz
Autogenerated HTML docs for v1.8.1.2-545-g2f19ad
Diffstat (limited to 'gitcli.html')
-rw-r--r--gitcli.html16
1 files changed, 8 insertions, 8 deletions
diff --git a/gitcli.html b/gitcli.html
index 50953cb8d..c5e711fe0 100644
--- a/gitcli.html
+++ b/gitcli.html
@@ -737,7 +737,7 @@ gitcli(7) Manual Page
<h2>NAME</h2>
<div class="sectionbody">
<p>gitcli -
- git command line interface and conventions
+ Git command line interface and conventions
</p>
</div>
</div>
@@ -751,7 +751,7 @@ gitcli(7) Manual Page
<div class="sect1">
<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
-<div class="paragraph"><p>This manual describes the convention used throughout git CLI.</p></div>
+<div class="paragraph"><p>This manual describes the convention used throughout Git CLI.</p></div>
<div class="paragraph"><p>Many commands take revisions (most often "commits", but sometimes
"tree-ish", depending on the context and command) and paths as their
arguments. Here are the rules:</p></div>
@@ -777,7 +777,7 @@ When an argument can be misunderstood as either a revision or a path,
</li>
<li>
<p>
-Without disambiguating <code>--</code>, git makes a reasonable guess, but errors
+Without disambiguating <code>--</code>, Git makes a reasonable guess, but errors
out and asking you to disambiguate when ambiguous. E.g. if you have a
file called HEAD in your work tree, <code>git diff HEAD</code> is ambiguous, and
you have to say either <code>git diff HEAD --</code> or <code>git diff -- HEAD</code> to
@@ -808,11 +808,11 @@ you will.</p></div>
</li>
</ul></div>
<div class="paragraph"><p>Here are the rules regarding the "flags" that you should follow when you are
-scripting git:</p></div>
+scripting Git:</p></div>
<div class="ulist"><ul>
<li>
<p>
-it&#8217;s preferred to use the non dashed form of git commands, which means that
+it&#8217;s preferred to use the non dashed form of Git commands, which means that
you should prefer <code>git foo</code> to <code>git-foo</code>.
</p>
</li>
@@ -856,7 +856,7 @@ many commands allow a long option "--option" to be abbreviated
<div class="sect1">
<h2 id="_enhanced_option_parser">ENHANCED OPTION PARSER</h2>
<div class="sectionbody">
-<div class="paragraph"><p>From the git 1.5.4 series and further, many git commands (not all of them at the
+<div class="paragraph"><p>From the Git 1.5.4 series and further, many Git commands (not all of them at the
time of the writing though) come with an enhanced option parser.</p></div>
<div class="paragraph"><p>Here is a list of the facilities provided by this option parser.</p></div>
<div class="sect2">
@@ -889,7 +889,7 @@ usage: git describe [options] &lt;committish&gt;*
</dt>
<dd>
<p>
- Some git commands take options that are only used for plumbing or that
+ Some Git commands take options that are only used for plumbing or that
are deprecated, and such options are hidden from the default usage. This
option gives the full list of options.
</p>
@@ -993,7 +993,7 @@ information.</p></div>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-10-10 15:49:24 PDT
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>