summaryrefslogtreecommitdiffstats
path: root/git-send-email.html
diff options
context:
space:
mode:
Diffstat (limited to 'git-send-email.html')
-rw-r--r--git-send-email.html13
1 files changed, 7 insertions, 6 deletions
diff --git a/git-send-email.html b/git-send-email.html
index 5abdf0c8d..05ab8cc50 100644
--- a/git-send-email.html
+++ b/git-send-email.html
@@ -832,11 +832,12 @@ and the "Subject:" of the message as the second line.</p></div>
Invoke a text editor (see GIT_EDITOR in <a href="git-var.html">git-var(1)</a>)
to edit an introductory message for the patch series.
</p>
-<div class="paragraph"><p>When <code>--compose</code> is used, git send-email will use the From, Subject, and
-In-Reply-To headers specified in the message. If the body of the message
-(what you type after the headers and a blank line) only contains blank
-(or Git: prefixed) lines, the summary won&#8217;t be sent, but From, Subject,
-and In-Reply-To headers will be used unless they are removed.</p></div>
+<div class="paragraph"><p>When <code>--compose</code> is used, git send-email will use the From, To, Cc, Bcc,
+Subject, Reply-To, and In-Reply-To headers specified in the message. If
+the body of the message (what you type after the headers and a blank
+line) only contains blank (or Git: prefixed) lines, the summary won&#8217;t be
+sent, but the headers mentioned above will be used unless they are
+removed.</p></div>
<div class="paragraph"><p>Missing From or In-Reply-To headers will be prompted for.</p></div>
<div class="paragraph"><p>See the CONFIGURATION section for <code>sendemail.multiEdit</code>.</p></div>
</dd>
@@ -1833,7 +1834,7 @@ Authen::SASL and Mail::Address.</p></div>
<div id="footer">
<div id="footer-text">
Last updated
- 2023-10-23 14:43:46 PDT
+ 2023-10-30 08:42:00 JST
</div>
</div>
</body>