summaryrefslogtreecommitdiffstats
path: root/git-send-email.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2017-03-21 15:40:14 -0700
committerJunio C Hamano <gitster@pobox.com>2017-03-21 15:40:14 -0700
commitcb06ef9e9d73f477240a2335194ce495c771b384 (patch)
tree1b8dc1b6497541d9cd0cc1243055ba583e2d9c12 /git-send-email.html
parentc53accfd680e0f0fd97ea63a917b47ef2d4109ab (diff)
downloadgit-htmldocs-cb06ef9e9d73f477240a2335194ce495c771b384.tar.gz
Autogenerated HTML docs for v2.12.1-430-gafd672
Diffstat (limited to 'git-send-email.html')
-rw-r--r--git-send-email.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/git-send-email.html b/git-send-email.html
index ef0d392b8..d653a99f4 100644
--- a/git-send-email.html
+++ b/git-send-email.html
@@ -859,7 +859,7 @@ and In-Reply-To headers will be used unless they are removed.</p></div>
reply to the given Message-Id, which avoids breaking threads to
provide a new patch series.
The second and subsequent emails will be sent as replies according to
- the <code>--[no]-chain-reply-to</code> setting.
+ the <code>--[no-]chain-reply-to</code> setting.
</p>
<div class="paragraph"><p>So for example when <code>--thread</code> and <code>--no-chain-reply-to</code> are specified, the
second and subsequent patches will be replies to the first one like in the
@@ -1550,7 +1550,7 @@ $ git send-email outgoing/*</code></pre>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2016-07-13 14:58:50 PDT
+Last updated 2017-03-21 15:39:58 PDT
</div>
</div>
</body>