summaryrefslogtreecommitdiffstats
path: root/git-send-email.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2023-10-30 08:44:11 +0900
committerJunio C Hamano <gitster@pobox.com>2023-10-30 08:44:11 +0900
commit918a697459a240f82a16fba9fe7a606ed1d9c2a9 (patch)
tree0ebdc5c599739be4b2c4fa4ebf0cfc1ebbbff565 /git-send-email.txt
parent33be82183d4cd6dc645f64da1402cf9a3f4cdbf3 (diff)
downloadgit-htmldocs-918a697459a240f82a16fba9fe7a606ed1d9c2a9.tar.gz
Autogenerated HTML docs for v2.42.0-526-g3130c1
Diffstat (limited to 'git-send-email.txt')
-rw-r--r--git-send-email.txt11
1 files changed, 6 insertions, 5 deletions
diff --git a/git-send-email.txt b/git-send-email.txt
index e90d04181..465011bad 100644
--- a/git-send-email.txt
+++ b/git-send-email.txt
@@ -68,11 +68,12 @@ This option may be specified multiple times.
Invoke a text editor (see GIT_EDITOR in linkgit:git-var[1])
to edit an introductory message for the patch series.
+
-When `--compose` 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't be sent, but From, Subject,
-and In-Reply-To headers will be used unless they are removed.
+When `--compose` 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't be
+sent, but the headers mentioned above will be used unless they are
+removed.
+
Missing From or In-Reply-To headers will be prompted for.
+