···97979898Follow these steps to backport a change into a release branch in compliance with the [commit policy](https://nixos.org/nixpkgs/manual/#submitting-changes-stable-release-branches).
9999100100+You can add a label such as `backport release-22.05` to a PR, so that merging it will
101101+automatically create a backport (via [a GitHub Action](.github/workflows/backport.yml)).
102102+This also works for PR's that have already been merged, and might take a couple of minutes to trigger.
103103+104104+You can also create the backport manually:
105105+1001061. Take note of the commits in which the change was introduced into `master` branch.
1011072. Check out the target _release branch_, e.g. `release-21.11`. Do not use a _channel branch_ like `nixos-21.11` or `nixpkgs-21.11-darwin`.
1021083. Create a branch for your change, e.g. `git checkout -b backport`.
···9292 <itemizedlist spacing="compact">
9393 <listitem>
9494 <para>
9595- Please remove this line when you add the first item since
9696- docbook requires the section to be non-empty
9595+ A new module was added for the Saleae Logic device family,
9696+ providing the options
9797+ <literal>hardware.saleae-logic.enable</literal> and
9898+ <literal>hardware.saleae-logic.package</literal>.
9799 </para>
98100 </listitem>
99101 </itemizedlist>
+2-1
nixos/doc/manual/release-notes/rl-2211.section.md
···44444545## Other Notable Changes {#sec-release-22.11-notable-changes}
46464747-- Please remove this line when you add the first item since docbook requires the section to be non-empty
4747+* A new module was added for the Saleae Logic device family, providing the options `hardware.saleae-logic.enable` and `hardware.saleae-logic.package`.
4848+4849<!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. -->