diff options
| author |  Ryan Anderson <ryan@michonline.com> | 2006-02-05 20:13:52 -0500 |
|---|---|---|
| committer |  Junio C Hamano <junkio@cox.net> | 2006-02-05 18:23:53 -0800 |
| commit | 2718435b7b746c3c249525b02fbcbad68f5a45f3 (patch) | |
| tree | 68a19468d086a2ed712bc53f1aafc99732a91e3c /Documentation | |
| parent | git-diff: use --cc instead of -p. (diff) | |
| download | tgif-2718435b7b746c3c249525b02fbcbad68f5a45f3.tar.xz | |
git-send-email: Fully implement --quiet and document it.
Also reorganizes the man page to list options alphabetically.
Signed-off-by: Ryan Anderson <ryan@michonline.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/git-send-email.txt | 44 |
1 files changed, 24 insertions, 20 deletions
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt index b9bec55e53..00537d8907 100644 --- a/Documentation/git-send-email.txt +++ b/Documentation/git-send-email.txt @@ -24,25 +24,23 @@ OPTIONS ------- The options available are: ---to:: - Specify the primary recipient of the emails generated. - Generally, this will be the upstream maintainer of the - project involved. +--chain-reply-to, --no-chain-reply-to:: + If this is set, each email will be sent as a reply to the previous + email sent. If disabled with "--no-chain-reply-to", all emails after + the first will be sent as replies to the first email sent. When using + this, it is recommended that the first file given be an overview of the + entire patch series. + Default is --chain-reply-to + +--compose:: + Use $EDITOR to edit an introductory message for the + patch series. --from:: Specify the sender of the emails. This will default to 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 @@ -50,18 +48,24 @@ The options available are: 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 - email sent. If disabled with "--no-chain-reply-to", all emails after - the first will be sent as replies to the first email sent. When using - this, it is recommended that the first file given be an overview of the - entire patch series. - Default is --chain-reply-to +--quiet:: + Make git-send-email less verbose. One line per email should be + all that is output. --smtp-server:: If set, specifies the outgoing SMTP server to use. Defaults to localhost. +--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. + +--to:: + Specify the primary recipient of the emails generated. + Generally, this will be the upstream maintainer of the + project involved. + Author ------ |