From 452332445af271ade214bd4aee12d3f03b5bd9e5 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 28 Sep 2012 13:14:42 -0700 Subject: documentation: dev-manual - wording change to remove ambiguity. (From yocto-docs rev: 01fc1959efa85fdba17beec4a5c565108c6ab68a) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-newbie.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'documentation') diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index ebae72e820..6beffc2f94 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml @@ -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: Provide a single-line, short summary of the change. -- cgit v1.2.3-54-g00ecf