Add "Past branches" page

ojeda · ojeda · commit 7554d3294823 · 2026-01-07T17:10:19.000+01:00
To avoid confusion (since the headers' nesting can be hard to see in the
rendered form), move all the past branches to a new, hidden page that is
linked from the existing "Past branches" section in the "Branches" page.

This reinstates the page as it was before removing some of the branches,
in later commits we will adjust them as needed.

Signed-off-by: Miguel Ojeda &lt;ojeda@kernel.org&gt;
diff --git a/SUMMARY.md b/SUMMARY.md
@@ -6,6 +6,7 @@
   - [Contributing](Contributing.md)
   - [Rust kernel policy](Rust-kernel-policy.md)
   - [Branches](Branches.md)
+  - Hidden [Past branches](Past-branches.md)
   - [Rust reference drivers](Rust-reference-drivers.md)
   - [Rust version policy](Rust-version-policy.md)
   - [Unstable features](Unstable-features.md)
diff --git a/src/Branches.md b/src/Branches.md
@@ -48,46 +48,4 @@ They are all part of [`linux-next`](https://git.kernel.org/pub/scm/linux/kernel/
 
 ## Past branches
 
-These branches are unmaintained, archived, deprecated, frozen or do not exist anymore in the repository.
-
-### `rust`
-
-[`rust`](https://github.com/Rust-for-Linux/linux/tree/rust) was the original branch where development happened for two years before Rust support was merged into the kernel.
-
-It contains most of the abstractions that the project worked on as a prototype/showcase. Some of those may eventually land upstream, others may be reworked with feedback from upstream, and a few may be dropped if unneeded.
-
-The branch is now archived, thus no new changes are merged into it. While it may be deleted eventually, for the moment it is kept around since some of the code did not make it upstream and may be useful for others.
-
-Similarly, its [Rust code documentation (2023-03-13)](https://rust-for-linux.github.io/docs/rust/kernel/) is archived as well.
-
-Changes to this branch landed via [GitHub PRs](https://github.com/Rust-for-Linux/linux/pulls). GitHub Actions was used as a pre-merge CI, compiling the kernel and booting it under QEMU for different toolchains, architectures and configurations. It also checked that some tests passed (e.g. loading sample modules, KUnit tests...) as well as building the PR under Clippy, building the docs, checking `rustfmt`, etc. [KernelCI](https://linux.kernelci.org/job/rust-for-linux/branch/rust/) tests it. Finally, in the past, the [Ksquirrel](Ksquirrel.md) bot checked the PRs sent to it.
-
-### `rust-dev`
-
-[`rust-dev`](https://github.com/Rust-for-Linux/linux/tree/rust-dev) is an experimental branch for integration purposes. It is a queue for patches that "look good enough".
-
-Its intended use cases are:
-
-  - Finding merge/apply conflicts as early as possible.
-  - Providing a common base for development that requires features that are not yet in mainline or `rust-next`, i.e. giving early access to features. This may include Rust-related changes from other subsystems, but it is not intended to cover our topic branches.
-  - Providing extra testing to patches by making them easily available to more developers.
-
-Note that this branch may be updated/rebased frequently and it might be gone in the future. Currently, it is on hold.
-
-### Topic branches (`staging/*`)
-
-These branches were focused on a particular topic and were meant to enable collaboration on code that is targeted for upstreaming but has not reached mainline yet.
-
-Some of these branches may contain work-in-progress code (similar to [staging trees](https://docs.kernel.org/process/2.Process.html?highlight=staging#staging-trees)) that may not be suitable for upstreaming or general usage yet. Please check the details of each branch.
-
-Changes to these branches land via GitHub PRs. Nevertheless, contributions should still follow the usual Linux kernel development process — see [Contributing](Contributing.md) for details.
-
-If you are interested in maintaining a new topic branch, then please [contact us](Contact.md). Thank you!
-
-#### `staging/rust-net`
-
-[`staging/rust-net`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-net) is dedicated to networking-related abstractions.
-
-The branch is kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features are welcome.
-
-It is maintained by Trevor Gross and Valentin Obst. Please contact them through [Zulip](Contact.md#zulip-chat).
+There are also other branches that are unmaintained, archived, deprecated, frozen or do not exist anymore in the repository. For historical details about these, please see our [Past branches](Past-branches.md) page.
diff --git a/src/Past-branches.md b/src/Past-branches.md
@@ -0,0 +1,67 @@
+## Past branches
+
+These branches are unmaintained, archived, deprecated, frozen or do not exist anymore in the repository.
+
+### `rust`
+
+[`rust`](https://github.com/Rust-for-Linux/linux/tree/rust) was the original branch where development happened for two years before Rust support was merged into the kernel.
+
+It contains most of the abstractions that the project worked on as a prototype/showcase. Some of those may eventually land upstream, others may be reworked with feedback from upstream, and a few may be dropped if unneeded.
+
+The branch is now archived, thus no new changes are merged into it. While it may be deleted eventually, for the moment it is kept around since some of the code did not make it upstream and may be useful for others.
+
+Similarly, its [Rust code documentation (2023-03-13)](https://rust-for-linux.github.io/docs/rust/kernel/) is archived as well.
+
+Changes to this branch landed via [GitHub PRs](https://github.com/Rust-for-Linux/linux/pulls). GitHub Actions was used as a pre-merge CI, compiling the kernel and booting it under QEMU for different toolchains, architectures and configurations. It also checked that some tests passed (e.g. loading sample modules, KUnit tests...) as well as building the PR under Clippy, building the docs, checking `rustfmt`, etc. [KernelCI](https://linux.kernelci.org/job/rust-for-linux/branch/rust/) tests it. Finally, in the past, the [Ksquirrel](Ksquirrel.md) bot checked the PRs sent to it.
+
+### `rust-dev`
+
+[`rust-dev`](https://github.com/Rust-for-Linux/linux/tree/rust-dev) is an experimental branch for integration purposes. It is a queue for patches that "look good enough".
+
+Its intended use cases are:
+
+  - Finding merge/apply conflicts as early as possible.
+  - Providing a common base for development that requires features that are not yet in mainline or `rust-next`, i.e. giving early access to features. This may include Rust-related changes from other subsystems, but it is not intended to cover our topic branches.
+  - Providing extra testing to patches by making them easily available to more developers.
+
+Note that this branch may be updated/rebased frequently and it might be gone in the future. Currently, it is on hold.
+
+### Topic branches (`staging/*`)
+
+These branches were focused on a particular topic and were meant to enable collaboration on code that is targeted for upstreaming but has not reached mainline yet.
+
+Some of these branches may contain work-in-progress code (similar to [staging trees](https://docs.kernel.org/process/2.Process.html?highlight=staging#staging-trees)) that may not be suitable for upstreaming or general usage yet. Please check the details of each branch.
+
+Changes to these branches land via GitHub PRs. Nevertheless, contributions should still follow the usual Linux kernel development process — see [Contributing](Contributing.md) for details.
+
+If you are interested in maintaining a new topic branch, then please [contact us](Contact.md). Thank you!
+
+#### `staging/dev`
+
+[`staging/dev`](https://github.com/Rust-for-Linux/linux/tree/staging/dev) is a branch intended to integrate the other topic branches (similar to the role of `rust-dev` for the main branches).
+
+It is maintained by Danilo Krummrich and Philipp Stanner. Please contact them through [Zulip](Contact.md#zulip-chat).
+
+#### `staging/rust-device`
+
+[`staging/rust-device`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-device) is dedicated to device/driver-related abstractions.
+
+The branch is kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features are welcome.
+
+It is maintained by Danilo Krummrich and Philipp Stanner. Please contact them through [Zulip](Contact.md#zulip-chat).
+
+#### `staging/rust-net`
+
+[`staging/rust-net`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-net) is dedicated to networking-related abstractions.
+
+The branch is kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features are welcome.
+
+It is maintained by Trevor Gross and Valentin Obst. Please contact them through [Zulip](Contact.md#zulip-chat).
+
+#### `staging/rust-pci`
+
+[`staging/rust-pci`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-pci) is dedicated to PCI-related abstractions, which are used by e.g. the [NVMe driver](NVMe-driver.md).
+
+The branch is kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features are welcome.
+
+Danilo Krummrich is `rust-pci`'s maintainer. You can also contact him through [Zulip](Contact.md#zulip-chat).
