# [PATCH] git-send-email.txt: describe --compose better

1 messages from 2009-03-16 to 2009-03-16. Participants: Stephen Boyd.
Thread: https://gitlist.dev/t/18319

## Stephen Boyd, 2009-03-16 07:44

Subject: [PATCH] git-send-email.txt: describe --compose better
Message-ID: <780e0a6b0903160044u301e65c7sc75e3f5b8230273c@mail.gmail.com>
URL: https://gitlist.dev/e/780e0a6b0903160044u301e65c7sc75e3f5b8230273c%40mail.gmail.com

```
Signed-off-by: Stephen Boyd <bebarino@gmail.com>
---
 Documentation/git-send-email.txt |   13 ++++++-------
 1 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index 14dfb50..10dfd66 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -60,14 +60,13 @@ The --cc option must be repeated for each user you
want on the cc list.
 	Use $GIT_EDITOR, core.editor, $VISUAL, or $EDITOR to edit an
 	introductory message for the patch series.
 +
-When '--compose' is used, git send-email gets less interactive will use the
-values of the headers you set there. If the body of the email (what you type
-after the headers and a blank line) only contains blank (or GIT: prefixed)
-lines, the summary won't be sent, but git-send-email will still use the
-Headers values if you don't removed them.
+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.
 +
-If it wasn't able to see a header in the summary it will ask you about it
-interactively after quitting your editor.
+Missing From or In-Reply-To headers will be prompted for.

 --from::
 	Specify the sender of the emails.  This will default to
-- 
1.6.2

```