[PATCH RFC3.5 12/12] Docs: send-email: git send-email -> 'send-email'
For the sake of consistency.
Signed-off-by: Michael Witten <mfwitten@gmail.com>
---
Documentation/git-send-email.txt | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index 3b36ac7..11965eb 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -59,7 +59,7 @@ 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 will use the From, Subject, and
+When '--compose' is used, '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,
@@ -244,7 +244,7 @@ Administering
--
- 'always' will always confirm before sending
- 'never' will never confirm before sending
-- 'cc' will confirm before sending when send-email has automatically
+- 'cc' will confirm before sending when 'send-email' has automatically
added addresses from the patch to the Cc list
- 'compose' will confirm before sending the first message when using --compose.
- 'auto' is equivalent to 'cc' + 'compose'
@@ -261,10 +261,10 @@ have been specified, in which case default to 'compose'.
When an argument may be understood either as a reference or as a file name,
choose to understand it as a format-patch argument ('--format-patch')
or as a file name ('--no-format-patch'). By default, when such a conflict
- occurs, git send-email will fail.
+ occurs, 'send-email' will fail.
--quiet::
- Make git-send-email less verbose. One line per email should be
+ Make 'send-email' less verbose. One line per email should be
all that is output.
--[no-]validate::
--
1.6.2.2.479.g2aec
Michael Witten <mfwitten@gmail.com>