···51515252In addition to writing properly formatted commit messages, it's important to include relevant information so other developers can later understand *why* a change was made. While this information usually can be found by digging code, mailing list/Discourse archives, pull request discussions or upstream changes, it may require a lot of work.
53535454-For package version upgrades and such a one-line commit message is usually sufficient.
5454+Package version upgrades usually allow for simpler commit messages, including attribute name, old and new version, as well as a reference to the relevant release notes/changelog. Every once in a while a package upgrade requires more extensive changes, and that subsequently warrants a more verbose message.
55555656## Rebasing between branches (i.e. from master to staging)
5757
···14641464 are under <literal>programs.firefox</literal>.
14651465 </para>
14661466 </listitem>
14671467+ <listitem>
14681468+ <para>
14691469+ The option
14701470+ <literal>services.picom.experimentalBackends</literal> was
14711471+ removed since it is now the default and the option will cause
14721472+ <literal>picom</literal> to quit instead.
14731473+ </para>
14741474+ </listitem>
14671475 </itemizedlist>
14681476 </section>
14691477</section>
+2
nixos/doc/manual/release-notes/rl-2211.section.md
···447447448448- A NixOS module for Firefox has been added which allows preferences and [policies](https://github.com/mozilla/policy-templates/blob/master/README.md) to be set. This also allows extensions to be installed via the `ExtensionSettings` policy. The new options are under `programs.firefox`.
449449450450+- The option `services.picom.experimentalBackends` was removed since it is now the default and the option will cause `picom` to quit instead.
451451+450452<!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. -->