[package] base-files: make build dependant on opkg/host

[openwrt.git] / docs / bugs.tex

diff --git a/docs/bugs.tex b/docs/bugs.tex
index b4f502c..9c46b5a 100644 (file)
--- a/docs/bugs.tex
+++ b/docs/bugs.tex
@@ -33,21 +33,6 @@ Once the ticket is open, a developer will take care of it, if so, the ticket is
 as "accepted" with the developer name. You can add comments at any time to the ticket,
 even when it is closed.
 
-\subsubsection{Submitting patches}
-
-In order to include a patch to a ticket, you need to output 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.
-
-Your patch must respect the following conventions :
-
-\begin{itemize}
-\item it has to work, with no side effect on other platforms, distributions, packages ...
-\item it must have a reason to be included in OpenWrt : bug fix, enhancement, feature adding/removing
-\item the patch name should be named like that : <index number>-this\_fixes\_bug\_foo\_and\_bar.patch
-\item if several, they have to be indexed with an integer number : 100-patch1, 200-patch2 ...
-\end{itemize}
-
-Your patch will be read and most likely be used as-is by the developpers if it is clean and working. If not, the patch will be accepted anyway and modified to be OpenWrt-rules compliant
-
 \subsubsection{Closing a ticket}
 
 A ticket might be closed by a developer because:
@@ -60,7 +45,7 @@ A ticket might be closed by a developer because:
 \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