Page MenuHomeFreeBSD

articles/problem-reports: cease recommending the patch keyword
ClosedPublic

Authored by grahamperrin on Oct 22 2022, 4:13 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 16, 9:35 PM
Unknown Object (File)
Fri, Dec 12, 7:28 AM
Unknown Object (File)
Wed, Dec 10, 10:30 PM
Unknown Object (File)
Thu, Nov 27, 10:09 AM
Unknown Object (File)
Nov 10 2025, 12:11 AM
Unknown Object (File)
Nov 4 2025, 8:00 PM
Unknown Object (File)
Nov 4 2025, 7:51 PM
Unknown Object (File)
Nov 4 2025, 7:51 PM
Subscribers

Details

Summary

Article 'Writing FreeBSD Problem Reports' pleads for use of a keyword:

patch

Keywords 'patch' and 'patch-ready' remain in Bugzilla, but should not be used. They are deprecated.

Update the article: end the plea, and explain why the available keywords should not be used.

PR: 267176, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267176.

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

grahamperrin created this revision.

For an edit of this type, I do not count myself as an author.

Six contributors, two authors (screenshot, GitHub):

image.png (527×618 px, 43 KB)

Incidentally: please, can someone delete https://reviews.freebsd.org/differential/diff/112096/? It's redundant.

Thanks

This revision is now accepted and ready to land.Oct 24 2022, 12:56 PM
…
% git -C /usr/doc apply /tmp/bug-267176.diff 
/tmp/bug-267176.diff:141: trailing whitespace.
* _If you have a patch, say so._ 
/tmp/bug-267176.diff:142: trailing whitespace.
The presence of a patch makes it much easier to progress a report. 
warning: 2 lines add whitespace errors.
%