summaryrefslogtreecommitdiffstats
path: root/git-rev-parse.html
diff options
context:
space:
mode:
authorJunio C Hamano <junio@kernel.org>2010-01-21 17:46:43 +0000
committerJunio C Hamano <junio@kernel.org>2010-01-21 17:46:43 +0000
commit1aa40d2e3f5186afb805e7020577acb9f5f78b89 (patch)
tree72812d480799e16b94f9cfed423b8d7d45c7fb4f /git-rev-parse.html
parenta9701f0184382d8de7380c56558718915905746a (diff)
downloadgit-htmldocs-1aa40d2e3f5186afb805e7020577acb9f5f78b89.tar.gz
Autogenerated HTML docs for v1.6.6.1-383-g5a9f
Diffstat (limited to 'git-rev-parse.html')
-rw-r--r--git-rev-parse.html36
1 files changed, 18 insertions, 18 deletions
diff --git a/git-rev-parse.html b/git-rev-parse.html
index 7f3664332..9018af282 100644
--- a/git-rev-parse.html
+++ b/git-rev-parse.html
@@ -326,9 +326,9 @@ git-rev-parse(1) Manual Page
<div class="sectionbody">
<div class="para"><p>Many git porcelainish commands take mixture of flags
(i.e. parameters that begin with a dash <em>-</em>) and parameters
-meant for the underlying <em>git-rev-list</em> command they use internally
+meant for the underlying <em>git rev-list</em> command they use internally
and flags and parameters for the other commands they use
-downstream of <em>git-rev-list</em>. This command is used to
+downstream of <em>git rev-list</em>. This command is used to
distinguish between them.</p></div>
</div>
<h2 id="_options">OPTIONS</h2>
@@ -339,7 +339,7 @@ distinguish between them.</p></div>
</dt>
<dd>
<p>
- Use <em>git-rev-parse</em> in option parsing mode (see PARSEOPT section below).
+ Use <em>git rev-parse</em> in option parsing mode (see PARSEOPT section below).
</p>
</dd>
<dt>
@@ -366,7 +366,7 @@ distinguish between them.</p></div>
</dt>
<dd>
<p>
- Use <em>git-rev-parse</em> in shell quoting mode (see SQ-QUOTE
+ Use <em>git rev-parse</em> in shell quoting mode (see SQ-QUOTE
section below). In contrast to the <tt>--sq</tt> option below, this
mode does only quoting. Nothing else is done to command input.
</p>
@@ -377,7 +377,7 @@ distinguish between them.</p></div>
<dd>
<p>
Do not output flags and parameters not meant for
- <em>git-rev-list</em> command.
+ <em>git rev-list</em> command.
</p>
</dd>
<dt>
@@ -386,7 +386,7 @@ distinguish between them.</p></div>
<dd>
<p>
Do not output flags and parameters meant for
- <em>git-rev-list</em> command.
+ <em>git rev-list</em> command.
</p>
</dd>
<dt>
@@ -446,7 +446,7 @@ distinguish between them.</p></div>
properly quoted for consumption by shell. Useful when
you expect your parameter to contain whitespaces and
newlines (e.g. when using pickaxe <tt>-S</tt> with
- <em>git-diff-*</em>). In contrast to the <tt>--sq-quote</tt> option,
+ <em>git diff-*</em>). In contrast to the <tt>--sq-quote</tt> option,
the command input is still interpreted as usual.
</p>
</dd>
@@ -609,7 +609,7 @@ distinguish between them.</p></div>
<dd>
<p>
Parse the date string, and output the corresponding
- --max-age= parameter for <em>git-rev-list</em>.
+ --max-age= parameter for <em>git rev-list</em>.
</p>
</dd>
<dt>
@@ -621,7 +621,7 @@ distinguish between them.</p></div>
<dd>
<p>
Parse the date string, and output the corresponding
- --min-age= parameter for <em>git-rev-list</em>.
+ --min-age= parameter for <em>git rev-list</em>.
</p>
</dd>
<dt>
@@ -653,7 +653,7 @@ The full SHA1 object name (40-byte hexadecimal string), or
</li>
<li>
<p>
-An output from <em>git-describe</em>; i.e. a closest tag, optionally
+An output from <em>git describe</em>; i.e. a closest tag, optionally
followed by a dash and a number of commits, followed by a dash, a
<tt>g</tt>, and an abbreviated object name.
</p>
@@ -700,13 +700,13 @@ otherwise, <tt>$GIT_DIR/refs/remotes/&lt;name&gt;/HEAD</tt> if exists.
</p>
<div class="para"><p>HEAD names the commit your changes in the working tree is based on.
FETCH_HEAD records the branch you fetched from a remote repository
-with your last <em>git-fetch</em> invocation.
+with your last <em>git fetch</em> invocation.
ORIG_HEAD is created by commands that moves your HEAD in a drastic
way, to record the position of the HEAD before their operation, so that
you can change the tip of the branch back to the state before you ran
them easily.
MERGE_HEAD records the commit(s) you are merging into your branch
-when you run <em>git-merge</em>.</p></div>
+when you run <em>git merge</em>.</p></div>
</li>
</ol></div>
</li>
@@ -847,7 +847,7 @@ J = F^2 = B^3^2 = A^^3^2</tt></pre>
</div>
<h2 id="_specifying_ranges">SPECIFYING RANGES</h2>
<div class="sectionbody">
-<div class="para"><p>History traversing commands such as <em>git-log</em> operate on a set
+<div class="para"><p>History traversing commands such as <em>git log</em> operate on a set
of commits, not just a single commit. To these commands,
specifying a single revision with the notation described in the
previous section means the set of commits reachable from that
@@ -884,7 +884,7 @@ F^! D G H D F</tt></pre>
</div>
<h2 id="_parseopt">PARSEOPT</h2>
<div class="sectionbody">
-<div class="para"><p>In <tt>--parseopt</tt> mode, <em>git-rev-parse</em> helps massaging options to bring to shell
+<div class="para"><p>In <tt>--parseopt</tt> mode, <em>git rev-parse</em> helps massaging options to bring to shell
scripts the same facilities C builtins have. It works as an option normalizer
(e.g. splits single switches aggregate values), a bit like <tt>getopt(1)</tt> does.</p></div>
<div class="para"><p>It takes on the standard input the specification of the options to parse and
@@ -892,7 +892,7 @@ understand, and echoes on the standard output a line suitable for <tt>sh(1)</tt>
to replace the arguments with normalized ones. In case of error, it outputs
usage on the standard error stream, and exits with code 129.</p></div>
<h3 id="_input_format">Input Format</h3><div style="clear:left"></div>
-<div class="para"><p><em>git-rev-parse --parseopt</em> input format is fully text based. It has two parts,
+<div class="para"><p><em>git rev-parse --parseopt</em> input format is fully text based. It has two parts,
separated by a line that contains only <tt>--</tt>. The lines before the separator
(should be more than one) are used for the usage.
The lines after the separator describe the options.</p></div>
@@ -972,12 +972,12 @@ eval `echo "$OPTS_SPEC" | git rev-parse --parseopt -- "$@" || echo exit $?`</tt>
</div>
<h2 id="_sq_quote">SQ-QUOTE</h2>
<div class="sectionbody">
-<div class="para"><p>In <tt>--sq-quote</tt> mode, <em>git-rev-parse</em> echoes on the standard output a
+<div class="para"><p>In <tt>--sq-quote</tt> mode, <em>git rev-parse</em> echoes on the standard output a
single line suitable for <tt>sh(1)</tt> <tt>eval</tt>. This line is made by
normalizing the arguments following <tt>--sq-quote</tt>. Nothing other than
quoting the arguments is done.</p></div>
<div class="para"><p>If you want command input to still be interpreted as usual by
-<em>git-rev-parse</em> before the output is shell quoted, see the <tt>--sq</tt>
+<em>git rev-parse</em> before the output is shell quoted, see the <tt>--sq</tt>
option.</p></div>
<h3 id="_example_2">Example</h3><div style="clear:left"></div>
<div class="listingblock">
@@ -1042,7 +1042,7 @@ Junio C Hamano &lt;gitster@pobox.com&gt; and Pierre Habouzit &lt;madcoder@debian
</div>
<div id="footer">
<div id="footer-text">
-Last updated 2010-01-21 00:41:40 UTC
+Last updated 2010-01-21 17:44:37 UTC
</div>
</div>
</body>