Lines Matching refs:or
6 …- The contribution should not break API or ABI, unless there is a real justification for that. If …
17 …s/issues) or [start a discussion](https://lists.trustedfirmware.org/mailman3/lists/mbed-tls.lists.…
19 1. Write a test which shows that the bug was fixed or that the feature works as expected.
21 1. For quick merging, the contribution should be short, and concentrated on a single feature or top…
28 …wer features, a newer generation of the library or a change has been necessary due to a security i…
30 …or API, even on the main development branch where new features are added, need to be justifiable b…
36 …with a new name, and whatever change is necessary, such as a new parameter or the addition of a re…
42 …without encountering additional features or API extensions which may introduce issues or change th…
46 1. Any change to the library which changes the API or ABI cannot be backported.
48 …ture or enhancement, no backporting is required. Exceptions to this may be additional test cases o…
57 As mentioned, tests that show the correctness of the feature or bug fix should be added to the pull…