- Update parts of this article and add a new "Tips and tricks for writing a good problem report" section.
- Fix a few typos.
- Add a link to the searchable gnats database at FreeBSD.org.
- Point the users at /usr/src/UPDATING for more info before sending PRs.
- Be more verbose about patches and inline inclusion of diffs in a PR.
- Emphasize the importance of Class: maintainer-update and the use of "[maintainer update]"
- Describe what "[patch]" in synopsis lines means now that it's commonly used to help people who read PR indexes.
Submitted by: Mark Linimon <linimon@lonesome.com>