This is not a hard rule: under special cirmstances branches can be useful.
They should not however be considered "routine".
-For advice on commit messages see
-[here](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html),
-and [here](https://github.com/torvalds/subsurface-for-dirk/blob/master/README.md#contributing)).
+For guidance on when branches are appropriate,
+see [[HDL_workflow/libresoc_bug_process]].
+
+For advice on commit messages see the Coding section further down on this page.
## yosys
### *Git commit message format*
-* Based on [bug #1126#c40](https://bugs.libre-soc.org/show_bug.cgi?id=1126#c40)
+* Additional articles on commit messages:
+ - [here](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
+
+ - [here](https://github.com/torvalds/subsurface-for-dirk/blob/master/README.md#contributing)).
+
+* LibreSOC message format based on description given in
+[bug #1126#c40](https://bugs.libre-soc.org/show_bug.cgi?id=1126#c40)
1. Every commit MUST start with a short title, up to 50 characters.
2. The commit title MUST contain either subsystem, or a file path,