diff options
| author | Junio C Hamano <gitster@pobox.com> | 2012-09-17 16:57:41 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2012-09-17 16:57:41 -0700 |
| commit | 281fd394a268e17e15f0869620a8f8fcaf28fbd1 (patch) | |
| tree | 2a23fd9bd63a0c0ab7ecd78e51be240177570fc3 /user-manual.txt | |
| parent | a3cfb7673d419cac3d57ad89e67537288d20696f (diff) | |
| download | git-htmldocs-281fd394a268e17e15f0869620a8f8fcaf28fbd1.tar.gz | |
Autogenerated HTML docs for v1.7.12-503-g59767
Diffstat (limited to 'user-manual.txt')
| -rw-r--r-- | user-manual.txt | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/user-manual.txt b/user-manual.txt index 03d95dc29..85651b57a 100644 --- a/user-manual.txt +++ b/user-manual.txt @@ -1136,9 +1136,12 @@ Creating good 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. +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. + [[ignoring-files]] Ignoring files |