Date: Sat, 10 May 2003 07:02:33 -0700 (PDT) From: Giorgos Keramidas <keramida@FreeBSD.org> To: doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: doc/en_US.ISO8859-1/articles/problem-reports article.sgml Message-ID: <200305101402.h4AE2X6g071014@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
keramida 2003/05/10 07:02:32 PDT
FreeBSD doc repository
Modified files:
en_US.ISO8859-1/articles/problem-reports article.sgml
Log:
- 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>
Revision Changes Path
1.24 +192 -20 doc/en_US.ISO8859-1/articles/problem-reports/article.sgml
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305101402.h4AE2X6g071014>