X-Git-Url: https://git.verplant.org/?a=blobdiff_plain;f=Documentation%2Fgit-send-email-script.txt;h=f79ad19945bd5f1cf81ca28dc785c0b68e20bc9b;hb=89580e3f6d671102bd8a7dda5f28cbfae2356269;hp=89f98bbf70a07138a0b9c92bccbfe595749bcb39;hpb=638ccfdf0eeabf3d985426308b2a82db6207ae28;p=git.git

diff --git a/Documentation/git-send-email-script.txt b/Documentation/git-send-email-script.txt
index 89f98bbf..f79ad199 100644
--- a/Documentation/git-send-email-script.txt
+++ b/Documentation/git-send-email-script.txt
@@ -1,5 +1,5 @@
 git-send-email-script(1)
-=======================
+========================
 v0.1, July 2005
 
 NAME
@@ -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