git_good_commits

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
git_good_commits [2019/04/03 20:28] – [U-Boot] rpjdaygit_good_commits [2023/07/18 06:50] (current) – rpjday
Line 15: Line 15:
  
   * Subject (first) line (followed by blank line):   * Subject (first) line (followed by blank line):
-    * 60 char max (including subsystem name) for''git log %%--%%oneline'').+    * 60 char max (including subsystem name) for ''git log %%--%%oneline'').
 <code> <code>
 8c7ae38d1ce1 afs: Fix StoreData op marshalling 8c7ae38d1ce1 afs: Fix StoreData op marshalling
Line 24: Line 24:
 047a013f8d0a chelsio: use BUG() instead of BUG_ON(1) 047a013f8d0a chelsio: use BUG() instead of BUG_ON(1)
 </code> </code>
-    * Be //accurate//.+    * Be //accurate//; the subject must describe the actual commit.
     * Use the imperative mood ("Fix", "Adjust", "Correct").     * Use the imperative mood ("Fix", "Adjust", "Correct").
     * Don't capitalize the first word.     * Don't capitalize the first word.
  • git_good_commits.1554323289.txt.gz
  • Last modified: 2019/04/03 20:28
  • by rpjday