[gentoo-doc-cvs] cvs commit: bugzilla-howto.xml

[Lukasz Damentko]

rane        06/09/02 05:26:46

  Modified:             bugzilla-howto.xml
  Log:
  #119053, added instructions about making diffs

Revision  Changes    Path
1.7                  xml/htdocs/doc/en/bugzilla-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.7&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.7&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.6&r2=1.7

Index: bugzilla-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- bugzilla-howto.xml	30 Aug 2005 02:51:12 -0000	1.6
+++ bugzilla-howto.xml	2 Sep 2006 05:26:46 -0000	1.7
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.6 2005/08/30 02:51:12 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.7 2006/09/02 05:26:46 rane Exp $ -->
 
 <guide link="/doc/en/bugzilla-howto.xml">
 <title>Gentoo Bug Reporting Guide</title>
@@ -20,8 +20,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.5</version>
-<date>2005-08-29</date>
+<version>1.6</version>
+<date>2006-09-01</date>
 
 <chapter>
 <title>Introduction</title>
@@ -1101,10 +1101,45 @@
 </p>
 
 <p>
-While we're doing all this, suppose another person finds your bug by searching
-through bugzilla and is curious to keep track of the bug, they may do so by
-putting their email in the Add CC field of the bug as shown below. You could
-also keep track of other bugs by following the same method.
+Sometimes a developer might ask you to attach a diff or patch for a file.
+Standard diff files can be obtained through:
+</p>
+
+<pre caption="Standard Diff Creation">
+$ <i>cp file file.old</i>
+$ <i>nano file</i>
+$ <i>diff -u file.old file</i>
+</pre>
+
+<p>
+For C/C++ source files, the <b>-p</b> flag is added to show what function calls
+the diff applies to:
+</p>
+
+<pre caption="Diff-ing C/C++ source">
+$ <i>cp file.c file.c.old</i>
+$ <i>nano file.c</i>
+$ <i>diff -up file.c.old file.c</i>
+</pre>
+
+<p>
+The documentation team will require the flag combination <b>-Nt</b> as well as
+<b>-u</b>. This mainly has to do with tab expansion.  You can create such a diff
+with:
+</p>
+
+<pre caption="Documentation diffs">
+$<i> cp file.xml file.xml.old</i>
+$<i> nano file.xml</i>
+$<i> diff -Nut file.xml.old file.xml</i>
+</pre>
+
+<p>
+And your diff is created. While we're doing all this, suppose another person
+finds your bug by searching through bugzilla and is curious to keep track of
+the bug, they may do so by putting their email in the Add CC field of the bug
+as shown below. You could also keep track of other bugs by following the same
+method.
 </p>
 
 <figure link="/images/docs/bugzie-add-email.png" caption="Adding Email To CC:"/>



-- 
gentoo-doc-cvs@g.o mailing list