yuzu-emu/mbedtls
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Wrap lines in the source to <80 columns

Browse source 
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
This commit is contained in:
Gilles Peskine 2021-06-07 20:44:47 +02:00
parent 87d36e311b
commit 6dd92c3f6b
1 changed files with 10 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
BRANCHES.md
View file

@ -28,14 +28,20 @@ undocumented features, then you should be able to re-compile it without
modification with any later release x.y'.z' with the same major version modification with any later release x.y'.z' with the same major version
number, and your code will still build, be secure, and work. number, and your code will still build, be secure, and work.
Note that new releases of Mbed TLS may extend the API. Here are some examples of changes that are common in minor releases of Mbed TLS, and are not considered API compatibility breaks: Note that new releases of Mbed TLS may extend the API. Here are some
examples of changes that are common in minor releases of Mbed TLS, and are
not considered API compatibility breaks:
* Adding or reordering fields in a structure or union. * Adding or reordering fields in a structure or union.
* Removing a field from a structure, unless the field is documented as public. * Removing a field from a structure, unless the field is documented as public.
* Adding items to an enum. * Adding items to an enum.
* Returning an error code that was not previously documented for a function when a new error condition arises. * Returning an error code that was not previously documented for a function
* Changing which error code is returned in a case where multiple error conditions apply. when a new error condition arises.
* Changing the behavior of a function from failing to succeeding, when the change is a reasonable extension of the current behavior, i.e. the addition of a new feature. * Changing which error code is returned in a case where multiple error
conditions apply.
* Changing the behavior of a function from failing to succeeding, when the
change is a reasonable extension of the current behavior, i.e. the
addition of a new feature.
There are rare exceptions where we break API compatibility: code that was There are rare exceptions where we break API compatibility: code that was
relying on something that became insecure in the meantime (for example, relying on something that became insecure in the meantime (for example,