git-send-email.txt: describe --compose better
Signed-off-by: Stephen Boyd <bebarino@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Stephen Boyd committed
Mar 16, 2009 at 00:44 UTC
01d386121758ac72aedd5f268feb763d53fc3cdf
1 file changed
+6
-7
Documentation/git-send-email.txt
+6
-7
@@ -60,14 +60,13 @@ The --cc option must be repeated for each user you want on the cc list.
60
Use $GIT_EDITOR, core.editor, $VISUAL, or $EDITOR to edit an
61
introductory message for the patch series.
62
+
63
-When '--compose' is used, git send-email gets less interactive will use the
64
-values of the headers you set there. If the body of the email (what you type
65
-after the headers and a blank line) only contains blank (or GIT: prefixed)
66
-lines, the summary won't be sent, but git-send-email will still use the
67
-Headers values if you don't removed them.
63
+When '--compose' is used, git send-email will use the From, Subject, and
64
+In-Reply-To headers specified in the message. If the body of the message
65
+(what you type after the headers and a blank line) only contains blank
66
+(or GIT: prefixed) lines the summary won't be sent, but From, Subject,
67
+and In-Reply-To headers will be used unless they are removed.
68
+
69
-If it wasn't able to see a header in the summary it will ask you about it
70
-interactively after quitting your editor.
69
+Missing From or In-Reply-To headers will be prompted for.
70
71
--from::
72
Specify the sender of the emails. This will default to