(Will update the errata template with the same change, once we have a suitable change)
Details
Details
- Reviewers
imp gjb markj - Group Reviewers
secteam - Commits
- R9:713410cb2ca0: Update advisory templates for Git
Diff Detail
Diff Detail
- Repository
- R9 FreeBSD doc repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
website/static/security/advisory-template.txt | ||
---|---|---|
119–120 | will replace sample hashes with XXXXXXXXXXXX |
website/static/security/advisory-template.txt | ||
---|---|---|
127–146 | Maybe just say 'for stable/13 and later', as releng/13.0 is branched from that. But I won't object if you decline this comment. |
website/static/security/advisory-template.txt | ||
---|---|---|
127–146 | Or maybe just "FreeBSD 13 and later"? |
website/static/security/advisory-template.txt | ||
---|---|---|
142 | Duplicate "run" I'd find the sentence easier to read if it were restructured, "run the following command to see which files were modified by a particular revision, replacing ..." |
website/static/security/advisory-template.txt | ||
---|---|---|
130 | A bit pedantic, but it looks like it should be "commit" instead of "hash". |
Comment Actions
A bit pedantic, but it looks like it should be "commit" instead of "hash".
Perhaps "modified in a particular commit hash"? I think I wanted to use hash in prose to match the <hash> in the example command, but agree the previous version didn't read that well.
website/static/security/advisory-template.txt | ||
---|---|---|
127–146 | Works for me. |