move the package dir to bin/packages/$(BOARD)_$(LIBC)-$(LIBCV) to prevent multiple...

[openwrt.git] / docs / bugs.tex

diff --git a/docs/bugs.tex b/docs/bugs.tex
index 9f0f4f0..9c46b5a 100644 (file)
--- a/docs/bugs.tex
+++ b/docs/bugs.tex
@@ -29,11 +29,6 @@ Regarding the kind of ticket that is open, a patch is welcome in those cases:
 \item new features that can be added by modifying existing OpenWrt files
 \end{itemize}
 
 \item new features that can be added by modifying existing OpenWrt files
 \end{itemize}
 

-In order to include a patch, you need to produce it, this can be done by using the 
-\textbf{svn diff} command which generates the differences between your local copy 
-(modified) and the version on the OpenWrt repository (unmodified yet). Then attach 
-the patch with a description, using the "Attach" button.
-

 Once the ticket is open, a developer will take care of it, if so, the ticket is marked
 as "accepted" with the developer name. You can add comments at any time to the ticket,
 even when it is closed.
 Once the ticket is open, a developer will take care of it, if so, the ticket is marked
 as "accepted" with the developer name. You can add comments at any time to the ticket,
 even when it is closed.


@@ -50,7 +45,7 @@ A ticket might be closed by a developer because:
 \item the problem cannot be reproduced by the developers (worksforme)
 \end{itemize}
 
 \item the problem cannot be reproduced by the developers (worksforme)
 \end{itemize}
 

-A the same time, the reporter may want to get the ticket closed since he is not 
+At the same time, the reporter may want to get the ticket closed since he is not 

 longer able to trigger the bug, or found it invalid by himself.
 
 When a ticket is closed by a developer and marked as "fixed", the comment contains 
 longer able to trigger the bug, or found it invalid by himself.
 
 When a ticket is closed by a developer and marked as "fixed", the comment contains