summaryrefslogtreecommitdiffstats
path: root/gittutorial.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 /gittutorial.txt
parenta3cfb7673d419cac3d57ad89e67537288d20696f (diff)
downloadgit-htmldocs-281fd394a268e17e15f0869620a8f8fcaf28fbd1.tar.gz
Autogenerated HTML docs for v1.7.12-503-g59767
Diffstat (limited to 'gittutorial.txt')
-rw-r--r--gittutorial.txt8
1 files changed, 5 insertions, 3 deletions
diff --git a/gittutorial.txt b/gittutorial.txt
index dee050567..f1cb6f3be 100644
--- a/gittutorial.txt
+++ b/gittutorial.txt
@@ -139,9 +139,11 @@ them to the index, and commit, all in one step.
A note on commit messages: 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.
+thorough description. 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.
Git tracks content not files
----------------------------