Date: Fri, 14 Jun 2019 09:41:35 +0000 (UTC) From: Mark Linimon <linimon@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53150 - head/en_US.ISO8859-1/articles/problem-reports Message-ID: <201906140941.x5E9fZZk055525@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: linimon Date: Fri Jun 14 09:41:35 2019 New Revision: 53150 URL: https://svnweb.freebsd.org/changeset/doc/53150 Log: Mention "svn diff" in Attaching Patches or Files. While here, try to make the paragraph make sense. Reviewed by: koobs Modified: head/en_US.ISO8859-1/articles/problem-reports/article.xml Modified: head/en_US.ISO8859-1/articles/problem-reports/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/problem-reports/article.xml Fri Jun 14 09:29:27 2019 (r53149) +++ head/en_US.ISO8859-1/articles/problem-reports/article.xml Fri Jun 14 09:41:35 2019 (r53150) @@ -539,10 +539,12 @@ <title>Attaching Patches or Files</title> <para>When attaching a patch, be sure to use - <option>-u</option> with &man.diff.1; - to create or unified diff - and make sure to specify the exact SVN revision numbers of the - files you modified so the developers who read your report will + either <command>svn diff</command> or + &man.diff.1; with the <option>-u</option> option + to create a unified diff + and make sure to specify the SVN revision number of the + repository against which you modified files, + so the developers who read your report will be able to apply them easily. For problems with the kernel or the base utilities, a patch against &os.current; (the HEAD Subversion branch) is preferred since all new code should be
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201906140941.x5E9fZZk055525>