mirror of
git://code.qt.io/qt/qt5.git
synced 2026-01-30 02:16:48 +08:00
f09783bb80
the change-id will be added at the end, which will look just plain stupid if the other "real" footers come above the changelog. also, a smart log author would integrate the changelog entry into the flow of the message, so further up in the template is more natural. Change-Id: I053840a81ea62f2e0ad1bd133f2e7a2692a6f2d6 Reviewed-by: Frederik Gladhorn <frederik.gladhorn@digia.com> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
33 lines
1.2 KiB
Plaintext
33 lines
1.2 KiB
Plaintext
# ==[ Subject: One line only short meaningful description for logs ]===|
|
|
|
|
|
|
# ==[ Details: Describe what changed and explain why it changed ]======|
|
|
|
|
|
|
# ==[ Footers: Uncomment and edit where applicable ]===================|
|
|
#
|
|
# Change log entry (see below for instructions).
|
|
#[ChangeLog][][]
|
|
#
|
|
# One task per entry. Remember space after colon.
|
|
#Task-number:
|
|
#
|
|
# Solicit reviewers. They still need to use the Gerrit frontend.
|
|
#Reviewed-by:
|
|
#
|
|
# ==[ Please wrap at 72 characters ]===================================|
|
|
#
|
|
# Remember to read http://wiki.qt-project.org/Commit_Policy
|
|
#
|
|
# 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.
|
|
# 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],
|
|
# [Platform Specific Changes][Windows][OS X][Linux/XCB].
|
|
#
|
|
# [ChangeLog][module][class/topic] description of the really important
|
|
# change that was just made on several lines.
|