User Tools

Site Tools


en:developers:documentation:submittingpatches

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:developers:documentation:submittingpatches [2022/04/01 11:27]
Kalle Valo [Fixes line is incorrect] Add example how to use git alias
en:developers:documentation:submittingpatches [2022/05/18 05:13]
Kalle Valo [Commit title is wrong] should be informative and unique
Line 13: Line 13:
 ===== Prior to sending patches ===== ===== Prior to sending patches =====
  
-Please **DO NOT** PGP sign patches sent to //​linux-wireless//​. The reason is that signing patches will encapsulate them into MIME and thereby mangle the patch. Also, please note that we prefer patches inline rather than attachments. ​+Please **DO NOT** PGP sign patches sent to public lists. The reason is that signing patches will encapsulate them into MIME and thereby mangle the patch. Also, please note that we prefer patches inline rather than attachments. And no HTML mail, our lists reject those automatically. 
 + 
 +And carefully read [[http://​www.infradead.org/​~dwmw2/​email.html|our email etiquette]],​ that saves everyone'​s time.
  
  
Line 363: Line 365:
 ==== Commit title is wrong ==== ==== Commit title is wrong ====
  
-The correc tformat ​for the commit title is name of driver, followed by a colon, followed by a space and then followed by the actual title. ​You can use ''​git log''​ to check older commits and see what prefix was used:+The correct format ​for the commit title is name of driver, followed by a colon, followed by a space and then followed by the actual title. ​Also the title should be informative and unique, so something like "fix a bug" is not a good title. 
 + 
 +For examples uou can use ''​git log''​ to check older commits and see what prefix was used:
  
 <​code>​ <​code>​
en/developers/documentation/submittingpatches.txt · Last modified: 2022/05/18 05:13 by Kalle Valo