aboutsummaryrefslogtreecommitdiff
path: root/docs/busybox.net/news.html
diff options
context:
space:
mode:
authorEric Andersen <andersen@codepoet.org>2005-01-13 17:15:34 +0000
committerEric Andersen <andersen@codepoet.org>2005-01-13 17:15:34 +0000
commit7d1b3d86856460e99b2a1b126e7eea9ea54f8af4 (patch)
tree3b21fd43cc8f5b50145d70dfc35c1e3f19a8f260 /docs/busybox.net/news.html
parent6077d90c26b1e102a6bb337c48821313111dc751 (diff)
downloadbusybox-7d1b3d86856460e99b2a1b126e7eea9ea54f8af4.tar.gz
Mention the new bug tracking system
Diffstat (limited to 'docs/busybox.net/news.html')
-rw-r--r--docs/busybox.net/news.html19
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/busybox.net/news.html b/docs/busybox.net/news.html
index 0d4c81bab..7796d6f95 100644
--- a/docs/busybox.net/news.html
+++ b/docs/busybox.net/news.html
@@ -3,6 +3,25 @@
<ul>
+ <li><b>13 January 2005 -- Bug and Patch Tracking</b><p>
+
+ Bug reports sometimes get lost when posted to the mailing list. The
+ developers of BusyBox are busy people, and have only so much they can keep
+ in their brains at a time. In my case, I'm lucky if I can remember my own
+ name, much less a bug report posted last week... To prevent your bug report
+ from getting lost, if you find a bug in BusyBox, please use the
+ <a href="http://bugs.busybox.net/">shiny new Bug and Patch Tracking System</a>
+ to post all the gory details.
+
+ <p>
+
+ The same applies to patches... Regardless of whether your patch
+ is a bug fix or adds spify new features, please post your patch
+ to the Bug and Patch Tracking System to make certain it is
+ properly considered.
+
+
+ <p>
<li><b>13 October 2004 -- BusyBox 1.00 released</b><p>
When you take a careful look at nearly every embedded Linux device or