atusb: Delete temporary file

[linux-libre-firmware.git] / CONTRIBUTING

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 18987c3b14968d1259c7b555c968af6261dfa97c..3a89d58531e9065aec2ba86f91e1f949951a2996 100644 (file)
--- 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.
 
 -   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
 -----------------------------
 
 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
 
 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:
 
 There are only two types of changes that can be made to a release
 branch:


@@ -56,10 +74,13 @@ 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.)
 
 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
 ---------
 
 Licensing
 ---------
 

-You can redistribute it and/or modify this file under the terms of the
+You can redistribute and/or modify this file under the terms of the

 GNU General Public License as published by the Free Software
 Foundation, either version 3 of the License, or (at your option) any
 later version.
 GNU General Public License as published by the Free Software
 Foundation, either version 3 of the License, or (at your option) any
 later version.