From 76ff1ac1da3396a505079e6e47788f5afb45bbbb Mon Sep 17 00:00:00 2001 From: Mark Linimon Date: Fri, 14 Jun 2019 09:41:35 +0000 Subject: [PATCH] Mention "svn diff" in Attaching Patches or Files. While here, try to make the paragraph make sense. Reviewed by: koobs --- en_US.ISO8859-1/articles/problem-reports/article.xml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/en_US.ISO8859-1/articles/problem-reports/article.xml b/en_US.ISO8859-1/articles/problem-reports/article.xml index 4881075300..7086bc2dd1 100644 --- a/en_US.ISO8859-1/articles/problem-reports/article.xml +++ b/en_US.ISO8859-1/articles/problem-reports/article.xml @@ -539,10 +539,12 @@ Attaching Patches or Files When attaching a patch, be sure to use - 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 svn diff or + &man.diff.1; with the 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