Searched full:guidelines (Results 1 – 25 of 115) sorted by relevance
12345
98 .Ss Assertion Guidelines109 Therefore, assertions should adhere to the following guidelines:180 According to the guidelines above, this would be correctly expressed as:
48 .Sh CODING GUIDELINES54 for a detailed set of rules and guidelines.
69 .%T "IANA Allocation Guidelines For Values In the \75 .%T "IANA Allocation Guidelines for the Protocol Field"
1 # Contribution Guidelines for GitHub5 Please read the guidelines in [Contributing to FreeBSD](https://docs.freebsd.org/en/articles/contri…50 …, please don't submit the raw results. Please also see the chunking up guidelines. Also, please ma…76 project. The guidelines are streamlined for quick decisions about each pull
37 This document presents guidelines for41 The guidelines for writing58 This document provides guidelines for balancing brevity and completeness
9 By using the following guidelines, you can help us make OpenZFS even better.153 * To verify your changes conform to the [style guidelines](206 Commit messages for new changes must meet the following guidelines:232 the commit message should meet the following guidelines:
112 … https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Standards-and-Guidelines/documents/exampl…142 … https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Standards-and-Guidelines/documents/exampl…
45 # remove static library from install (fedora packaging guidelines)115 - Using Fedoraproject wiki guidelines.
23 guidelines:111 9. Guidelines how to integrate error output of new crypto library modules
23 <li class="inline"><a href="#guidelines">Guidelines for Adding Configuration Commands </a></li>29 … description of the files used in the configuration process as well as guidelines on how to constr…159 <h4 id="guidelines">Guidelines for Adding Configuration Commands</h4>
9 [guidelines for contributing](../CONTRIBUTING.md).
21 A priority ranging from 0 to 255 according to the following guidelines::
32 the following guidelines:
2 FreeBSD Quirk Guidelines27 Please follow these guidelines to get your device working as soon
87 * Be careful of stylistic errors in your code (see below for style guidelines).103 * Follow standard Git commit message guidelines. The first line has a maximum
13 Guidelines for new compatibles for SoC blocks/components.
21 CONTRIBUTION GUIDELINES FOR string SUB-DIRECTORY
1 Guidelines for contributing
18 new. These guidelines aren't new, but they desperately need to be
1 GENERIC CONTRIBUTION GUIDELINES
50 Later sections suggest guidelines to be used in modifying
24 We have a separate document with [contribution guidelines](./.github/CONTRIBUTING.md).
36 are welcomed, but please follow the OpenBSD style guidelines[1].
5 Community contributions are welcome as long as they align with the [project priorities](https://github.com/PJK/libcbor#main-features) and [goals](https://libcbor.readthedocs.io/en/latest/development.html#goals) and follow the guidelines described below.
70 .Ss Hook Naming Guidelines