diff options
| author | Mark Linimon <linimon@FreeBSD.org> | 2019-06-14 09:41:35 +0000 |
|---|---|---|
| committer | Mark Linimon <linimon@FreeBSD.org> | 2019-06-14 09:41:35 +0000 |
| commit | 76ff1ac1da3396a505079e6e47788f5afb45bbbb (patch) | |
| tree | ab11293447460968165d461955e20352cf326e17 | |
| parent | c1280cafc1c1c475bbb6a6c185dc84ef73e04be3 (diff) | |
| download | doc-76ff1ac1da.tar.gz doc-76ff1ac1da.zip | |
Mention "svn diff" in Attaching Patches or Files. While here, try to
make the paragraph make sense.
Reviewed by: koobs
Notes
Notes:
svn path=/head/; revision=53150
| -rw-r--r-- | en_US.ISO8859-1/articles/problem-reports/article.xml | 10 |
1 files 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 @@ <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 |