summaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorStef Walter <stefw@collabora.co.uk>2011-01-20 13:36:33 -0600
committerStef Walter <stefw@collabora.co.uk>2011-01-21 14:48:43 -0600
commita50ba779ff3e0a5d4f35fb2b6ab525a423575cc4 (patch)
tree0ba036aa541c3a243effbb50e7ff79c89bf4709f /ChangeLog
Initial implementation of p11-unity
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog31
1 files changed, 31 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
new file mode 100644
index 0000000..88f5857
--- /dev/null
+++ b/ChangeLog
@@ -0,0 +1,31 @@
+=== ChangeLog is autogenerated ===
+
+ p11-unity relys on commit messages to provide change history. Please
+ write commit messages in the following format:
+
+=== begin example commit ===
+
+ Short explanation of the commit
+
+ Longer explanation explaining exactly what's changed, whether any
+ external or private interfaces changed, what bugs were fixed (with bug
+ tracker reference if applicable) and so forth. Be concise but not too
+ brief.
+
+=== end example commit ===
+
+ - Always add a brief description of the commit to the _first_ line of
+ the commit and terminate by two newlines. This may be the title of
+ a fixed bug, copied from Bugzilla.
+
+ - First line (the brief description) must only be one sentence and
+ should start with a capital letter unless it starts with a
+ lowercase symbol or identifier. Don't use a trailing full stop,
+ and don't exceed 72 characters.
+
+ - The main description (the body) is normal prose and should use
+ normal punctuation and capital letters where appropriate.
+
+ - When committing code on behalf of others use the --author option,
+ e.g. git commit -a --author "Joe Coder <joe@coder.org>" and
+ --signoff.