os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Mention "svn diff" in Attaching Patches or Files. While here, try to

Browse source 
make the paragraph make sense.

Reviewed by:	koobs
This commit is contained in:
Mark Linimon 2019-06-14 09:41:35 +00:00
parent c1280cafc1
commit 76ff1ac1da
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=53150
1 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
en_US.ISO8859-1/articles/problem-reports/article.xml
View file

@ -539,10 +539,12 @@
<title>Attaching Patches or Files</title> <title>Attaching Patches or Files</title>
<para>When attaching a patch, be sure to use <para>When attaching a patch, be sure to use
<option>-u</option> with &man.diff.1; either <command>svn diff</command> or
to create or unified diff &man.diff.1; with the <option>-u</option> option
and make sure to specify the exact SVN revision numbers of the to create a unified diff
files you modified so the developers who read your report will 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 be able to apply them easily. For problems with the kernel or
the base utilities, a patch against &os.current; (the HEAD the base utilities, a patch against &os.current; (the HEAD
Subversion branch) is preferred since all new code should be Subversion branch) is preferred since all new code should be