svn commit: r49017 - head/en_US.ISO8859-1/books/porters-handbook/quick-porting
Mathieu Arnold
mat at FreeBSD.org
Tue Jun 28 16:06:58 UTC 2016
Author: mat
Date: Tue Jun 28 16:06:57 2016
New Revision: 49017
URL: https://svnweb.freebsd.org/changeset/doc/49017
Log:
Tell people that using svn diff for submitting new ports is ok.
Reviewed by: wblock
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D7006
Modified:
head/en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml
Modified: head/en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml Tue Jun 28 16:06:54 2016 (r49016)
+++ head/en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml Tue Jun 28 16:06:57 2016 (r49017)
@@ -372,14 +372,25 @@ lib/X11/oneko/mouse.xpm</programlisting>
Reports and General Commentary</link> for more information
submitting problem reports.</para> -->
- <para>To submit <filename>oneko.shar</filename>, use the <link
- xlink:href="https://bugs.freebsd.org/submit/">bug submit
- form</link> (category <literal>Ports Tree</literal>).
- Add a short
- description of the program to the Description field of the PR
- (perhaps a short version of <varname>COMMENT</varname>), and
- do not forget to add <filename>oneko.shar</filename> as an
- attachment.</para>
+ <para>A diff created from a <application>Subversion</application>
+ checkout of the ports tree is also acceptable. Add all the
+ files with <command>svn add</command>. <command>cd</command> to
+ the base of the ports tree so full paths to the changed files
+ are included in the diff, then generate the diff with
+ <command>svn diff</command>. For example, <command>svn diff
+ games/oneko > oneko.diff</command>.</para>
+
+ <para>Submit <filename>oneko.shar</filename> or
+ <filename>oneko.diff</filename> with the <link
+ xlink:href="https://bugs.freebsd.org/submit/">bug submission
+ form</link>.. Use product <quote>Ports &
+ Packages</quote>, component <quote>Individual Port(s)</quote>,
+ and follow the guidelines shown there.
+ Add a short description of the program to the Description field
+ of the PR (perhaps a short version of
+ <varname>COMMENT</varname>), and remember to add
+ <filename>oneko.shar</filename> or
+ <filename>oneko.diff</filename> as an attachment.</para>
<note>
<para>Giving a good description in the summary of the problem
More information about the svn-doc-head
mailing list