summaryrefslogtreecommitdiffstats
path: root/git-commit.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2012-09-17 16:57:41 -0700
committerJunio C Hamano <gitster@pobox.com>2012-09-17 16:57:41 -0700
commit281fd394a268e17e15f0869620a8f8fcaf28fbd1 (patch)
tree2a23fd9bd63a0c0ab7ecd78e51be240177570fc3 /git-commit.txt
parenta3cfb7673d419cac3d57ad89e67537288d20696f (diff)
downloadgit-htmldocs-281fd394a268e17e15f0869620a8f8fcaf28fbd1.tar.gz
Autogenerated HTML docs for v1.7.12-503-g59767
Diffstat (limited to 'git-commit.txt')
-rw-r--r--git-commit.txt6
1 files changed, 4 insertions, 2 deletions
diff --git a/git-commit.txt b/git-commit.txt
index 4622297ec..9594ac8e9 100644
--- a/git-commit.txt
+++ b/git-commit.txt
@@ -389,8 +389,10 @@ DISCUSSION
Though not required, it's a good idea to begin the commit message
with a single short (less than 50 character) line summarizing the
change, followed by a blank line and then a more thorough description.
-Tools that turn commits into email, for example, use the first line
-on the Subject: line and the rest of the commit in the body.
+The text up to the first blank line in a commit message is treated
+as the commit title, and that title is used throughout git.
+For example, linkgit:git-format-patch[1] turns a commit into email, and it uses
+the title on the Subject line and the rest of the commit in the body.
include::i18n.txt[]