Terminate <para> elements before starting a new <screen> and

clarify a bit the part that describes the type of patches we
like sending upstream for ports.
This commit is contained in:
Giorgos Keramidas 2009-05-13 02:05:11 +00:00
parent 8cac9e4dbc
commit dd3676854b
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=34267

View file

@ -172,7 +172,8 @@
</listitem>
<listitem>
<para>If you have contributed any ports, send your patches
<para>If you have contributed any ports and you had to make
&os;-specific changes, send your patches
back to the original authors (this will make your life
easier when they bring out the next version).</para>
</listitem>
@ -341,22 +342,24 @@
<para>For example:</para>
<para>
<screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
<screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
or
<para>or</para>
<screen>&prompt.user; <userinput>diff -c -r olddir newdir</userinput></screen>
<screen>&prompt.user; <userinput>diff -c -r olddir newdir</userinput></screen>
would generate such a set of context diffs for the given
<para>would generate such a set of context diffs for the given
source file or directory hierarchy.</para>
<para>Likewise,
<screen>&prompt.user; <userinput>diff -u oldfile newfile</userinput></screen>
or
<screen>&prompt.user; <userinput>diff -u -r olddir newdir</userinput></screen>
<para>Likewise,</para>
would do the same, except in the unified diff format.</para>
<screen>&prompt.user; <userinput>diff -u oldfile newfile</userinput></screen>
<para>or</para>
<screen>&prompt.user; <userinput>diff -u -r olddir newdir</userinput></screen>
<para>would do the same, except in the unified diff format.</para>
<para>See the manual page for &man.diff.1; for more details.</para>