diff options
author | Junio C Hamano <gitster@pobox.com> | 2013-09-17 14:34:00 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-09-17 14:34:00 -0700 |
commit | e6f28d0b6c239f15760194c8b12afdaa1a7bdd34 (patch) | |
tree | b782d1e78feb1a9f17131581d754b0e29abaa0b8 /git-fast-import.html | |
parent | 0e0e0d2656a57fd3628bb6dbdaf0096684ed24a9 (diff) | |
download | git-htmldocs-e6f28d0b6c239f15760194c8b12afdaa1a7bdd34.tar.gz |
Autogenerated HTML docs for v1.8.4-357-g8d83
Diffstat (limited to 'git-fast-import.html')
-rw-r--r-- | git-fast-import.html | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/git-fast-import.html b/git-fast-import.html index 0939b4a59..53fb5f2b4 100644 --- a/git-fast-import.html +++ b/git-fast-import.html @@ -1264,8 +1264,8 @@ change to the project.</p></div> ('author' (SP <name>)? SP LT <email> GT SP <when> LF)?
'committer' (SP <name>)? SP LT <email> GT SP <when> LF
data
- ('from' SP <committish> LF)?
- ('merge' SP <committish> LF)?
+ ('from' SP <commit-ish> LF)?
+ ('merge' SP <commit-ish> LF)?
(filemodify | filedelete | filecopy | filerename | filedeleteall | notemodify)*
LF?</code></pre>
</div></div>
@@ -1334,8 +1334,8 @@ Omitting the <code>from</code> command on existing branches is usually desired, as the current commit on that branch is automatically assumed to
be the first ancestor of the new commit.</p></div>
<div class="paragraph"><p>As <code>LF</code> is not valid in a Git refname or SHA-1 expression, no
-quoting or escaping syntax is supported within <code><committish></code>.</p></div>
-<div class="paragraph"><p>Here <code><committish></code> is any of the following:</p></div>
+quoting or escaping syntax is supported within <code><commit-ish></code>.</p></div>
+<div class="paragraph"><p>Here <code><commit-ish></code> is any of the following:</p></div>
<div class="ulist"><ul>
<li>
<p>
@@ -1393,7 +1393,7 @@ However Git’s other tools never create commits with more than 15 additional ancestors (forming a 16-way merge). For this reason
it is suggested that frontends do not use more than 15 <code>merge</code>
commands per commit; 16, if starting a new, empty branch.</p></div>
-<div class="paragraph"><p>Here <code><committish></code> is any of the commit specification expressions
+<div class="paragraph"><p>Here <code><commit-ish></code> is any of the commit specification expressions
also accepted by <code>from</code> (see above).</p></div>
</div>
<div class="sect3">
@@ -1594,8 +1594,8 @@ paths for a commit are encouraged to do so.</p></div> <div class="sect3">
<h4 id="_code_notemodify_code"><code>notemodify</code></h4>
<div class="paragraph"><p>Included in a <code>commit</code> <code><notes_ref></code> command to add a new note
-annotating a <code><committish></code> or change this annotation contents.
-Internally it is similar to filemodify 100644 on <code><committish></code>
+annotating a <code><commit-ish></code> or change this annotation contents.
+Internally it is similar to filemodify 100644 on <code><commit-ish></code>
path (maybe split into subdirectories). It’s not advised to
use any other commands to write to the <code><notes_ref></code> tree except
<code>filedeleteall</code> to delete all existing notes in this tree.
@@ -1613,7 +1613,7 @@ External data format </p>
<div class="literalblock">
<div class="content">
-<pre><code> 'N' SP <dataref> SP <committish> LF</code></pre>
+<pre><code> 'N' SP <dataref> SP <commit-ish> LF</code></pre>
</div></div>
<div class="paragraph"><p>Here <code><dataref></code> can be either a mark reference (<code>:<idnum></code>)
set by a prior <code>blob</code> command, or a full 40-byte SHA-1 of an
@@ -1630,13 +1630,13 @@ Inline data format </p>
<div class="literalblock">
<div class="content">
-<pre><code> 'N' SP 'inline' SP <committish> LF
+<pre><code> 'N' SP 'inline' SP <commit-ish> LF
data</code></pre>
</div></div>
<div class="paragraph"><p>See below for a detailed description of the <code>data</code> command.</p></div>
</dd>
</dl></div>
-<div class="paragraph"><p>In both formats <code><committish></code> is any of the commit specification
+<div class="paragraph"><p>In both formats <code><commit-ish></code> is any of the commit specification
expressions also accepted by <code>from</code> (see above).</p></div>
</div>
</div>
@@ -1666,7 +1666,7 @@ lightweight (non-annotated) tags see the <code>reset</code> command below.</p></ <div class="literalblock">
<div class="content">
<pre><code> 'tag' SP <name> LF
- 'from' SP <committish> LF
+ 'from' SP <commit-ish> LF
'tagger' (SP <name>)? SP LT <email> GT SP <when> LF
data</code></pre>
</div></div>
@@ -1704,10 +1704,10 @@ branch from an existing commit without creating a new commit.</p></div> <div class="literalblock">
<div class="content">
<pre><code> 'reset' SP <ref> LF
- ('from' SP <committish> LF)?
+ ('from' SP <commit-ish> LF)?
LF?</code></pre>
</div></div>
-<div class="paragraph"><p>For a detailed description of <code><ref></code> and <code><committish></code> see above
+<div class="paragraph"><p>For a detailed description of <code><ref></code> and <code><commit-ish></code> see above
under <code>commit</code> and <code>from</code>.</p></div>
<div class="paragraph"><p>The <code>LF</code> after the command is optional (it used to be required).</p></div>
<div class="paragraph"><p>The <code>reset</code> command can also be used to create lightweight
@@ -2444,7 +2444,7 @@ compression.</p></div> <div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-09-12 16:24:44 PDT
+Last updated 2013-09-17 14:33:14 PDT
</div>
</div>
</body>
|