From: Ryan Anderson Date: Mon, 05 Sep 2005 05:13:07 GMT Subject: [PATCH 2/2] Update documentation of --compose to git-send-email-script.txt Message-ID: <11258971872608-git-send-email-ryan@michonline.com> In-Reply-To: <1125897187857-git-send-email-ryan@michonline.com> Signed-off-by: Ryan Anderson --- Documentation/git-send-email-script.txt | 13 +++++++++---- 1 files changed, 9 insertions(+), 4 deletions(-) 60765e20aa12da748f43204e25cb582f88fb16c8 diff --git a/Documentation/git-send-email-script.txt b/Documentation/git-send-email-script.txt --- a/Documentation/git-send-email-script.txt +++ b/Documentation/git-send-email-script.txt @@ -33,16 +33,21 @@ The options available are: the value GIT_COMMITTER_IDENT, as returned by "git-var -l". The user will still be prompted to confirm this entry. + --compose + Use \$EDITOR to edit an introductory message for the + patch series. + --subject Specify the initial subject of the email thread. + Only necessary if --compose is also set. If --compose + is not set, this will be prompted for. --in-reply-to Specify the contents of the first In-Reply-To header. Subsequent emails will refer to the previous email - instead of this. - When overriding on the command line, it may be necessary - to set this to a space. For example - --in-reply-to=" " + instead of this if --chain-reply-to is set (the default) + Only necessary if --compose is also set. If --compose + is not set, this will be prompted for. --chain-reply-to, --no-chain-reply-to If this is set, each email will be sent as a reply to the previous