summaryrefslogtreecommitdiffstats
path: root/git-format-patch.html
diff options
context:
space:
mode:
Diffstat (limited to 'git-format-patch.html')
-rw-r--r--git-format-patch.html24
1 files changed, 12 insertions, 12 deletions
diff --git a/git-format-patch.html b/git-format-patch.html
index f092febbc..b069e3a1e 100644
--- a/git-format-patch.html
+++ b/git-format-patch.html
@@ -757,10 +757,10 @@ git-format-patch(1) Manual Page
[--signature-file=<file>]
[-n | --numbered | -N | --no-numbered]
[--start-number <n>] [--numbered-files]
- [--in-reply-to=<message id>] [--suffix=.<sfx>]
+ [--in-reply-to=<message-id>] [--suffix=.<sfx>]
[--ignore-if-in-upstream] [--always]
[--cover-from-description=<mode>]
- [--rfc] [--subject-prefix=<subject prefix>]
+ [--rfc] [--subject-prefix=<subject-prefix>]
[(--reroll-count|-v) <n>]
[--to=<email>] [--cc=<email>]
[--[no-]cover-letter] [--quiet]
@@ -770,8 +770,8 @@ git-format-patch(1) Manual Page
[--range-diff=<previous> [--creation-factor=<percent>]]
[--filename-max-length=<n>]
[--progress]
- [<common diff options>]
- [ &lt;since&gt; | &lt;revision range&gt; ]</pre>
+ [&lt;common-diff-options&gt;]
+ [ &lt;since&gt; | &lt;revision-range&gt; ]</pre>
<div class="attribution">
</div></div>
</div>
@@ -820,7 +820,7 @@ A single commit, &lt;since&gt;, specifies that the commits leading
</li>
<li>
<p>
-Generic &lt;revision range&gt; expression (see "SPECIFYING
+Generic &lt;revision-range&gt; expression (see "SPECIFYING
REVISIONS" section in <a href="gitrevisions.html">gitrevisions(7)</a>) means the
commits in the specified range.
</p>
@@ -1166,7 +1166,7 @@ and accumulating child directory counts in the parent directories:
</dt>
<dd>
<p>
- Synonym for --dirstat=files,param1,param2&#8230;
+ Synonym for --dirstat=files,&lt;param1&gt;,&lt;param2&gt;&#8230;
</p>
</dd>
<dt class="hdlist1">
@@ -1782,12 +1782,12 @@ itself. If you want <code>git format-patch</code> to take care of threading, yo
will want to ensure that threading is disabled for <code>git send-email</code>.</p></div>
</dd>
<dt class="hdlist1">
---in-reply-to=&lt;message id&gt;
+--in-reply-to=&lt;message-id&gt;
</dt>
<dd>
<p>
Make the first mail (or all the mails with <code>--no-thread</code>) appear as a
- reply to the given &lt;message id&gt;, which avoids breaking threads to
+ reply to the given &lt;message-id&gt;, which avoids breaking threads to
provide a new patch series.
</p>
</dd>
@@ -1843,12 +1843,12 @@ populated with placeholder text.</p></div>
</p>
</dd>
<dt class="hdlist1">
---subject-prefix=&lt;subject prefix&gt;
+--subject-prefix=&lt;subject-prefix&gt;
</dt>
<dd>
<p>
Instead of the standard <em>[PATCH]</em> prefix in the subject
- line, instead use <em>[&lt;subject prefix&gt;]</em>. This can be used
+ line, instead use <em>[&lt;subject-prefix&gt;]</em>. This can be used
to name a patch series, and can be combined with the
<code>--numbered</code> option.
</p>
@@ -2144,7 +2144,7 @@ you can use <code>--suffix=-patch</code> to get <code>0001-description-of-my-cha
</dt>
<dd>
<p>
- Treat the revision argument as a &lt;revision range&gt;, even if it
+ Treat the revision argument as a &lt;revision-range&gt;, even if it
is just a single commit (that would normally be treated as a
&lt;since&gt;). Note that root commits included in the specified
range are always formatted as creation patches, independently
@@ -2618,7 +2618,7 @@ merge commit.</p></div>
<div id="footer">
<div id="footer-text">
Last updated
- 2023-12-18 14:49:41 PST
+ 2024-02-08 15:45:59 PST
</div>
</div>
</body>