You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/Past-branches.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
##Past branches
1
+
# Past branches
2
2
3
3
These branches are unmaintained, archived, deprecated, frozen or do not exist anymore in the repository.
4
4
5
-
###`rust`
5
+
## `rust`
6
6
7
7
[`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.
8
8
@@ -14,7 +14,7 @@ Similarly, its [Rust code documentation (2023-03-13)](https://rust-for-linux.git
14
14
15
15
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.
16
16
17
-
###`rust-dev`
17
+
## `rust-dev`
18
18
19
19
[`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".
20
20
@@ -26,7 +26,7 @@ Its intended use cases are:
26
26
27
27
Note that this branch may be updated/rebased frequently and it might be gone in the future. Currently, it is on hold.
28
28
29
-
###Topic branches (`staging/*`)
29
+
## Topic branches (`staging/*`)
30
30
31
31
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.
32
32
@@ -36,29 +36,29 @@ Changes to these branches land via GitHub PRs. Nevertheless, contributions shoul
36
36
37
37
If you are interested in maintaining a new topic branch, then please [contact us](Contact.md). Thank you!
38
38
39
-
####`staging/dev`
39
+
### `staging/dev`
40
40
41
41
[`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).
42
42
43
43
It is maintained by Danilo Krummrich and Philipp Stanner. Please contact them through [Zulip](Contact.md#zulip-chat).
44
44
45
-
####`staging/rust-device`
45
+
### `staging/rust-device`
46
46
47
47
[`staging/rust-device`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-device) is dedicated to device/driver-related abstractions.
48
48
49
49
The branch is kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features are welcome.
50
50
51
51
It is maintained by Danilo Krummrich and Philipp Stanner. Please contact them through [Zulip](Contact.md#zulip-chat).
52
52
53
-
####`staging/rust-net`
53
+
### `staging/rust-net`
54
54
55
55
[`staging/rust-net`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-net) is dedicated to networking-related abstractions.
56
56
57
57
The branch is kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features are welcome.
58
58
59
59
It is maintained by Trevor Gross and Valentin Obst. Please contact them through [Zulip](Contact.md#zulip-chat).
60
60
61
-
####`staging/rust-pci`
61
+
### `staging/rust-pci`
62
62
63
63
[`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).
0 commit comments