Create ChangeLog entry correcting the record on #4044 #4893
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The change made by PR Mbed-TLS#4044 was previously advertised in the 2.16.10 ChangeLog, however Mbed-TLS#4044 had not yet been merged. Create a new entry for Mbed-TLS#4044, with a note that the previous entry was in error. Signed-off-by: David Horstmann <david.horstmann@arm.com>
davidhorstmann-arm
added
needs-review
yanesca
added
needs-preceding-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE: Do not merge this PR before #4044 is merged! (Lest we have to do this a second time.)
Partial fix for #4870.
A ChangeLog entry was created for #4044 by mistake in the 2.16.10 release, without #4044 having been merged. This PR creates a new ChangeLog entry explaining that the previous ChangeLog entry was incorrect, but that the fix has now been merged.
Status
READY
Requires Backporting
NO
Migrations
If there is any API change, what's the incentive and logic for it.
NO
Todos