Lines Matching +full:- +full:- +full:add +full:- +full:architecture

9 [conduct]: https://www.rust-lang.org/conduct.html
16 [issues]: https://github.com/nix-rust/nix/issues
22 issues][issue-search] to see if there's something related. If not, just
23 [open a new issue][new-issue]!
27 include the OS and version, and the architecture.
29 [issue-search]: https://github.com/nix-rust/nix/search?utf8=%E2%9C%93&q=is%3Aissue&type=Issues
30 [new-issue]: https://github.com/nix-rust/nix/issues/new
36 issue][new-issue] requesting it. As with reporting a bug, the more
43 [Rust's issue labeling scheme][rust-labels]:
44 - **A-** prefixed labels state which area of the project the issue
46 - **E-** prefixed labels explain the level of experience necessary to fix the
48 - **O-** prefixed labels specify the OS for issues that are OS-specific
49 - **R-** prefixed labels specify the architecture for issues that are
50   architecture-specific
52 [rust-labels]: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#issue-triage
58 some [great documentation][pr-docs] on using the Pull Request feature. We use the 'fork and
64 you fix a bug, please add an appropriate note to the [change log][cl]. We
67 [cl]: https://github.com/nix-rust/nix/blob/master/CHANGELOG.md
68 [kacl]: https://github.com/olivierlacan/keep-a-changelog/tree/18adb5f5be7a898d046f6a4acb93e39dcf40c…
69 [pr-docs]: https://help.github.com/articles/using-pull-requests/
75 add a test that would have failed without the fix.
79 Cirrus-CI][cirrus-ci], which might find some issues on other platforms. The CI
83 locally.  More information is available in the [CI Readme][ci-readme].
85 [cirrus-ci]: https://cirrus-ci.com/github/nix-rust/nix
86 [ci-readme]: ci/README.md
91 To stop a test from running under CI, add `skip_if_cirrus!()` to it. Please
106 [bors]: https://bors-ng.github.io/
114 [conventions]: https://github.com/nix-rust/nix/blob/master/CONVENTIONS.md