diff options
| author | Neal H. Walfield <neal@pep.foundation> | 2023-05-22 12:23:10 +0200 |
|---|---|---|
| committer | Neal H. Walfield <neal@pep.foundation> | 2023-06-02 12:15:44 +0200 |
| commit | 06da5ff602182181b92de2d1d3c11b131b39d08f (patch) | |
| tree | f4a8542116a71672f910dfeb70921687f33605d5 | |
| parent | 11b11b73d911962a8396c0f6bc57612fdfd25adc (diff) | |
doc: Fix markdown.neal/markdown
- For some reason, a list was formatted as a code block. Fix it.
| -rw-r--r-- | doc/security-vulnerabilities.md | 38 |
1 files changed, 19 insertions, 19 deletions
diff --git a/doc/security-vulnerabilities.md b/doc/security-vulnerabilities.md index 4235dc7d..193453f0 100644 --- a/doc/security-vulnerabilities.md +++ b/doc/security-vulnerabilities.md @@ -40,25 +40,25 @@ disclosure, and publish a fix as soon as possible. 1. Create and test a minimal patch - - Candidate versions: - - The latest version - - The version in Debian stable - - The version in Debian testing, if testing is frozen - - Minor versions before an MSRV bump (i.e., if 1.x bumps the MSRV - consider patching 1.x-1). - - Downstreams may request patches for specific versions. - If approved, add them to this list. (Note: companies should be a - partner, or have a support contract with us.) - - - Suggestions: - - For testing purposes, gather all tests into a single file. It - is then easy to drop the test into any version of the code - base and see if it is affected. - - Because we want the patch to cleanly apply to many versions, - don't append new tests to a sequence of unit tests. This is - because the unit tests are normally appended to, and this will - very likely result in a merge conflict with earlier versions. - Either prepend the test, or add it to a new file. + - Candidate versions: + - The latest version + - The version in Debian stable + - The version in Debian testing, if testing is frozen + - Minor versions before an MSRV bump (i.e., if 1.x bumps the MSRV + consider patching 1.x-1). + - Downstreams may request patches for specific versions. + If approved, add them to this list. (Note: companies should be a + partner, or have a support contract with us.) + + - Suggestions: + - For testing purposes, gather all tests into a single file. It + is then easy to drop the test into any version of the code + base and see if it is affected. + - Because we want the patch to cleanly apply to many versions, + don't append new tests to a sequence of unit tests. This is + because the unit tests are normally appended to, and this will + very likely result in a merge conflict with earlier versions. + Either prepend the test, or add it to a new file. 1. Reach out to downstreams (see list below): |