X-Git-Url: https://jxself.org/git/?p=linux-libre-firmware.git;a=blobdiff_plain;f=CONTRIBUTING;h=94523be23ce0a61cb4d2b0a2a88721cc7cbb3292;hp=18987c3b14968d1259c7b555c968af6261dfa97c;hb=7a03ed46b9746db8e1107a7d1914ef139df8a63e;hpb=d758389b6d1f9d1e6a7ed2c4f13bbabf21e6bffd

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 18987c3..94523be 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -28,6 +28,24 @@ message to the GNU Linux-libre mailing list:
 -   Your patch must also update the root level Makefile to build the
     firmware, as appropriate.
 
+Git Commit Messages
+-------------------
+
+-   Limit the subject to 50 characters.
+
+-   Use proper capitalization and imperative mood in the subject.
+
+-   Don't put a period at the end of the subject.
+
+-   Small changes, like fixing a typo, can get by with only a subject.
+    Larger changes should include a body too.
+
+-   Use a blank line to separate the subject and body.
+
+-   Use the body to explain the what and why of the change.
+
+-   Wrap the body at 70 characters.
+
 Development & Release Process
 -----------------------------
 
@@ -40,8 +58,8 @@ between versions.
 
 Every change, no matter how well-intentioned, introduces the potential
 for unexpected problems. For this reason changes on a release branch
-are more stringent, as opposed to "anything can change" philosophy of
-the master branch.
+are more stringent, as opposed to the "anything can change" 
+philosophy of the master branch.
 
 There are only two types of changes that can be made to a release
 branch:
@@ -56,6 +74,9 @@ Updates for a released version involve adding a third point to the
 version number: 1.2.1, etc. and this third point is incremented by 1
 with every release (1.2.2, 1.2.3, etc.)
 
+There is no timetable for releases: New versions are released when 
+they're ready. Updates to release branches are made as needed.
+
 Licensing
 ---------