Proofread CVE fix versions in vdr.xml
#7
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
To check the changes to the VDR file it is easier to: - have a `latest.xml` file which contains the current status. - copy it to `<n>.xml` when we make modifications. This way we can follow the history of the `latest.xml` file for changes.
See #6 for references to the commits that implement the fixes.
vy
reviewed
Jan 28, 2025
Exactly, the way we currently do it (new document at each update), you need to checkout the commit to see the differences. |
|
@ppkarwasz, since version 2 was incorrectly bumped, can we override |
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.
This is the
vdr.xmlequivalent of the changes introduced in #6. Therefore, it requires #6 to be merged first.