Lines Matching +full:unix +full:- +full:like

8 If you want to add your changes to v0.2, please submit them to the `libc-0.2` branch.
29 platforms of that level. For example, when adding a Unix API it should be added
30 to `src/unix/mod.rs`, but when adding a Linux-only API it should be added to
31 `src/unix/linux_like/linux/mod.rs`.
39 symbols list(s) found in the `libc-test/semver` directory. These lists keep
42 all supported Unixes it should be added to `unix.txt` list<sup>1</sup>,
53 <sup>1</sup>: Note that this list has nothing to do with any Unix or Posix
54 standard, it's just a list shared between all OSs that declare `#[cfg(unix)]`.
58 We have two automated tests running on [GitHub Actions](https://github.com/rust-lang/libc/actions):
60 1. [`libc-test`](https://github.com/gnzlbg/ctest)
61   - `cd libc-test && cargo test`
62   - Use the `skip_*()` functions in `build.rs` if you really need a workaround.
64   - [`sh ci/style.sh`](https://github.com/rust-lang/libc/blob/main/ci/style.sh)
70 `libc` crate successfully. It's annoying to do the equivalent of semver-major versioning
75   - The `since` field should have a next version of `libc`
77   - The `note` field should have a reason to deprecate and a tracking issue to call for comments
91 it. If you'd like to get a release out ASAP you can follow these steps:
93 1. Increment the patch version number in `Cargo.toml` and `libc-test/Cargo.toml`.
94 1. Send a PR to this repository. It should [look like this][example-pr], but it'd
100 [example-pr]: https://github.com/rust-lang/libc/pull/2120