aboutsummaryrefslogtreecommitdiffstats
path: root/toolchain
ModeNameSize
-rw-r--r--Config.in8239logstatsplain
-rw-r--r--Makefile2976logstatsplain
d---------binutils107logstatsplain
d---------uClibc303logstatsplain
d---------wrapper36logstatsplain
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-29 13:04:03 +0000
om OpenWrt \end{itemize} Regarding the kind of ticket that is open, a patch is welcome in those cases: \begin{itemize} \item new package to be included in OpenWrt \item fix for a bug that works for the reporter and has no known side effect \item new features that can be added by modifying existing OpenWrt files \end{itemize} 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. \subsubsection{Closing a ticket} A ticket might be closed by a developer because: \begin{itemize} \item the problem is already fixed (wontfix) \item the problem described is not judged as valid, and comes along with an explanation why (invalid) \item the developers know that this bug will be fixed upstream (wontfix) \item the problem is very similar to something that has already been reported (duplicate) \item the problem cannot be reproduced by the developers (worksforme) \end{itemize} 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 the subversion changeset which corrects the bug.