From dbac1e77f79ff99945cea41522f535132cacc692 Mon Sep 17 00:00:00 2001 From: Oswald Buddenhagen Date: Mon, 25 Nov 2013 11:45:03 +0100 Subject: try to make the ChangeLog template more inviting move it even futher up and encourage integrating it into the rest of the commit message. Change-Id: I5aaa417a58d420c3d3a8d5ca80dcd9f265c64829 Reviewed-by: Sergio Ahumada Reviewed-by: Marc Mutz Reviewed-by: Frederik Gladhorn Reviewed-by: Thiago Macieira --- .commit-template | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.commit-template b/.commit-template index 0aef528f..813ca689 100644 --- a/.commit-template +++ b/.commit-template @@ -4,10 +4,10 @@ # ==[ Details: Describe what changed and explain why it changed ]======| -# ==[ Footers: Uncomment and edit where applicable ]===================| -# # Change log entry (see below for instructions). #[ChangeLog][][] + +# ==[ Footers: Uncomment and edit where applicable ]===================| # # One task per entry. Remember space after colon. #Task-number: @@ -22,7 +22,8 @@ # Change log entry: If this commit adds a significant feature, fixes an # issue or contains a behavior change that is relevant to others, # add a change log entry. It can be multiple lines long and ends with an -# empty newline. +# empty newline. Try to integrate it into the flow of the commit message +# to avoid redundancy. # Use the module name to indicate the area of the change e.g. [QtCore]. # Optionally specify a class or subtopic [QtNetwork][QSslSocket]. # Other common tags are: [General], [Important Behavior Changes], -- cgit v1.2.3