diff options
author | Junio C Hamano <junio@hera.kernel.org> | 2009-03-18 01:54:48 +0000 |
---|---|---|
committer | Junio C Hamano <junio@hera.kernel.org> | 2009-03-18 01:54:48 +0000 |
commit | ea82cff53ef3184e59a2e9e334f99284248e8b35 (patch) | |
tree | 772babff00e6437b22c2096d0b22c39eed6e3951 /git-send-email.txt | |
parent | 064b4ab54285c3775f9f7a98235a28b0becfcebb (diff) | |
download | git-htmldocs-ea82cff53ef3184e59a2e9e334f99284248e8b35.tar.gz |
Autogenerated HTML docs for v1.6.2.1-147-g642d0
Diffstat (limited to 'git-send-email.txt')
-rw-r--r-- | git-send-email.txt | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/git-send-email.txt b/git-send-email.txt index 14dfb501e..10dfd667b 100644 --- a/git-send-email.txt +++ b/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 |