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
These branches are unmaintained, archived, deprecated, frozen or do not exist anymore in the repository.
3
+
These branches are unmaintained, archived, deprecated, frozen or do not exist anymore in the repository. Historical details about them follow.
4
4
5
5
## `rust`
6
6
@@ -16,52 +16,50 @@ Changes to this branch landed via [GitHub PRs](https://github.com/Rust-for-Linux
16
16
17
17
## `rust-dev`
18
18
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".
19
+
[`rust-dev`](https://github.com/Rust-for-Linux/linux/tree/rust-dev)was an experimental branch for integration purposes. It was a queue for patches that "looked good enough".
20
20
21
-
Its intended use cases are:
21
+
Its intended use cases were:
22
22
23
23
- Finding merge/apply conflicts as early as possible.
24
-
- 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.
24
+
- 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 was not intended to cover our topic branches.
25
25
- Providing extra testing to patches by making them easily available to more developers.
26
26
27
-
Note that this branch may be updated/rebased frequently and it might be gone in the future. Currently, it is on hold.
27
+
This branch was intended to be updated/rebased frequently.
28
28
29
29
## Topic branches (`staging/*`)
30
30
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.
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. The intention was to make it easy to request/add new ones.
32
32
33
33
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.
34
34
35
-
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.
36
-
37
-
If you are interested in maintaining a new topic branch, then please [contact us](Contact.md). Thank you!
35
+
Changes to these branches landed via GitHub PRs. Nevertheless, contributions should still follow the usual Linux kernel development process — see [Contributing](Contributing.md) for details.
38
36
39
37
### `staging/dev`
40
38
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).
39
+
[`staging/dev`](https://github.com/Rust-for-Linux/linux/tree/staging/dev)was a branch intended to integrate the other topic branches (similar to the role of `rust-dev` for the main branches).
42
40
43
-
It is maintained by Danilo Krummrich and Philipp Stanner. Please contact them through [Zulip](Contact.md#zulip-chat).
41
+
It was maintained by Danilo Krummrich and Philipp Stanner. You could contact them through [Zulip](Contact.md#zulip-chat).
44
42
45
43
### `staging/rust-device`
46
44
47
-
[`staging/rust-device`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-device)is dedicated to device/driver-related abstractions.
45
+
[`staging/rust-device`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-device)was dedicated to device/driver-related abstractions.
48
46
49
-
The branch is kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features are welcome.
47
+
The branch was kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features were welcome.
50
48
51
-
It is maintained by Danilo Krummrich and Philipp Stanner. Please contact them through [Zulip](Contact.md#zulip-chat).
49
+
It was maintained by Danilo Krummrich and Philipp Stanner. You could contact them through [Zulip](Contact.md#zulip-chat).
52
50
53
51
### `staging/rust-net`
54
52
55
-
[`staging/rust-net`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-net)is dedicated to networking-related abstractions.
53
+
[`staging/rust-net`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-net)was dedicated to networking-related abstractions.
56
54
57
-
The branch is kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features are welcome.
55
+
The branch was kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features were welcome.
58
56
59
-
It is maintained by Trevor Gross and Valentin Obst. Please contact them through [Zulip](Contact.md#zulip-chat).
57
+
It was maintained by Trevor Gross and Valentin Obst. You could contact them through [Zulip](Contact.md#zulip-chat).
60
58
61
59
### `staging/rust-pci`
62
60
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).
61
+
[`staging/rust-pci`](https://github.com/Rust-for-Linux/linux/tree/staging/rust-pci)was dedicated to PCI-related abstractions, which were used by e.g. the [NVMe driver](NVMe-driver.md).
64
62
65
-
The branch is kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features are welcome.
63
+
The branch was kept in a compilable state (rebased regularly on top of `rust-next` or mainline). Fixes and features were welcome.
66
64
67
-
Danilo Krummrich is `rust-pci`'s maintainer. You can also contact him through [Zulip](Contact.md#zulip-chat).
65
+
It was maintained by Danilo Krummrich. You could contact him through [Zulip](Contact.md#zulip-chat).
0 commit comments