+In the case of bug fixes, the patch's subject must be prefixed with
+`Fix:` and a suitable sub-system name. For instance, a patch
+addressing a bug in the session daemon should start with `Fix:
+sessiond:`. Patches targeting shared code can either use the namespace
+of the interface or of the internal library, whichever is more
+precise.
+
+A non-exhaustive list of common sub-system prefixes follows:
+
+ * `relayd` (relay daemon).
+ * `sessiond` (session daemon).
+ * `lttng` (LTTng CLI client).
+ * `ust-consumerd` (user space consumer daemon).
+ * `kernel-consumerd` (kernel space consumer daemon).
+ * `consumerd` (common consumer daemon).
+ * `common` (internal `libcommon`).
+ * `trace-chunk` (internal `lttng_trace_chunk_*` interface).
+ * `lttng-ctl` (`liblttng-ctl` library).
+ * `mi` (LTTng client's machine interface).
+
+When possible, the commit title should describe the issue _as
+observed_ and not the underlying cause. For instance, prefer `Fix:
+sessiond: hang on SIGTERM after session rotation` to `Fix: sessiond:
+unchecked status on exit`.
+
+The commit message's body must be as detailed as possible and explain
+the reasons behind the proposed change. Keep in mind that this message
+will be read in a number of years and must still be clear. Any related