Lines Matching refs:or

24 …s/issues) or [start a discussion](https://lists.trustedfirmware.org/mailman3/lists/mbed-tls.lists.…
26 1. Write a test which shows that the bug was fixed or that the feature works as expected.
28 1. For quick merging, the contribution should be short, and concentrated on a single feature or top…
33 …wer features, a newer generation of the library or a change has been necessary due to a security i…
35 …or API, even on the main development branch where new features are added, need to be justifiable b…
37 …ion with one that has a slightly different interface (different prototype, or different documented…
43 …without encountering additional features or API extensions which may introduce issues or change th…
47 1. Any change to the library which changes the API or ABI cannot be backported.
49 …ture or enhancement, no backporting is required. Exceptions to this may be additional test cases o…
58 As mentioned, tests that show the correctness of the feature or bug fix should be added to the pull…
87 …tps://spdx.org/licenses/Apache-2.0.html) OR [GPL-2.0-or-later](https://spdx.org/licenses/GPL-2.0-o…
89 …ions are made under both the Apache-2.0 AND [GPL-2.0-or-later](https://spdx.org/licenses/GPL-2.0-o…
91 … license identifier where possible, i.e. "SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later".
95 …come part of the project, and is submitted under both the Apache-2.0 AND GPL-2.0-or-later licenses.