summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJenkins <jenkins@review.openstack.org>2012-08-30 02:19:00 +0000
committerGerrit Code Review <review@openstack.org>2012-08-30 02:19:00 +0000
commit3c665eaada07388a77977995cd1f5b3e26370ec5 (patch)
treebe0875f491d981143a683c5a7a8451532324684b
parent5d8290e36b85c0ad3cb068937b176364635d8da0 (diff)
parent701549ce0d1b76e37d5ca80f677db037edef48d0 (diff)
downloadnova-3c665eaada07388a77977995cd1f5b3e26370ec5.tar.gz
nova-3c665eaada07388a77977995cd1f5b3e26370ec5.tar.xz
nova-3c665eaada07388a77977995cd1f5b3e26370ec5.zip
Merge "hacking: Add driver prefix recommendation."
-rw-r--r--HACKING.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/HACKING.rst b/HACKING.rst
index 96805b4d8..52dc38bf8 100644
--- a/HACKING.rst
+++ b/HACKING.rst
@@ -235,6 +235,10 @@ readable. Follow these guidelines:
description of the change, not just a reference to a bug or
blueprint. It must be followed by a single blank line.
+ If the change relates to a specific driver (libvirt, xenapi, qpid, etc...),
+ begin the first line of the commit message with the driver name, lowercased,
+ followed by a colon.
+
Following your brief summary, provide a more detailed description of
the patch, manually wrapping the text at 72 characters. This
description should provide enough detail that one does not have to