path: root/Documentation/git-send-email.txt
diff options
authorThomas Ackermann <>2013-01-21 19:16:20 (GMT)
committerJunio C Hamano <>2013-02-01 21:53:25 (GMT)
commit48a8c26c625a4d3631c4f614bceb38933e741408 (patch)
tree97b1a550b575ecd250370cac842ecba58aa93d87 /Documentation/git-send-email.txt
parentfe73786b482f11e7a37a269c95d222a384fc5a39 (diff)
Documentation: avoid poor-man's small caps GIT
In the earlier days, we used to spell the name of the system as GIT, to simulate as if it were typeset with capital G and IT in small caps. Later we stopped doing so at around 1.6.5 days. Let's stop doing so throughout the documentation. The name to refer to the whole system (and the concept it embodies) is "Git"; the command end-users type is "git". And document this in the coding guideline. Signed-off-by: Thomas Ackermann <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-send-email.txt')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index eeb561c..44a1f7c 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -67,7 +67,7 @@ The --cc option must be repeated for each user you want on the cc list.
When '--compose' is used, git 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,
+(or Git: prefixed) lines the summary won't be sent, but From, Subject,
and In-Reply-To headers will be used unless they are removed.
Missing From or In-Reply-To headers will be prompted for.