documentation: dev-manual - wording change to remove ambiguity.

(From yocto-docs rev: 01fc1959efa85fdba17beec4a5c565108c6ab68a)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2012-09-28 13:14:42 -07:00 committed by Richard Purdie
parent 8cd203a46c
commit 452332445a
1 changed files with 2 additions and 1 deletions

View File

@ -992,7 +992,8 @@
should almost always provide a more detailed description of what you did (i.e.
the body of the commit message).
The only exceptions for not providing a detailed description would be if your
change is a simple, self-explanatory change that needs no description.
change is a simple, self-explanatory change that needs no further description
beyond the summary.
Here are the guidelines for composing a commit message:
<itemizedlist>
<listitem><para>Provide a single-line, short summary of the change.