Skip to content

doc: remove security reporting examples

Keep things concise and tell people to report stuff if in doubt.

This may be controversial (although I hope not). In my opinion, the level of detail provided seems to be geared towards discouraging reports by making things seem unnecessarily complicated or nuanced.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

Merge request reports

Loading