send-email docs: add format-patch options
git-send-email(1) does not mention that "git format-patch" options are accepted. Augment SYNOPSIS and DESCRIPTION to mention it. Update git-send-email.perl USAGE to be consistent with git-send-email(1). Signed-off-by: Thiago Perrotta <tbperrotta@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
2b7b75850c
commit
a2ce608244
@ -9,7 +9,8 @@ git-send-email - Send a collection of patches as emails
|
||||
SYNOPSIS
|
||||
--------
|
||||
[verse]
|
||||
'git send-email' [<options>] <file|directory|rev-list options>...
|
||||
'git send-email' [<options>] <file|directory>...
|
||||
'git send-email' [<options>] <format-patch options>
|
||||
'git send-email' --dump-aliases
|
||||
|
||||
|
||||
@ -19,7 +20,8 @@ Takes the patches given on the command line and emails them out.
|
||||
Patches can be specified as files, directories (which will send all
|
||||
files in the directory), or directly as a revision list. In the
|
||||
last case, any format accepted by linkgit:git-format-patch[1] can
|
||||
be passed to git send-email.
|
||||
be passed to git send-email, as well as options understood by
|
||||
linkgit:git-format-patch[1].
|
||||
|
||||
The header of the email is configurable via command-line options. If not
|
||||
specified on the command line, the user will be prompted with a ReadLine
|
||||
|
@ -40,7 +40,8 @@ package main;
|
||||
|
||||
sub usage {
|
||||
print <<EOT;
|
||||
git send-email [options] <file | directory | rev-list options >
|
||||
git send-email' [<options>] <file|directory>
|
||||
git send-email' [<options>] <format-patch options>
|
||||
git send-email --dump-aliases
|
||||
|
||||
Composing:
|
||||
|
Loading…
Reference in New Issue
Block a user