7d1b3d868
Eric Andersen
2005-01-13
Subject
Mention the new bug tracking system
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
docs/busybox.net/header.html+1 -0
| @@ -51,6 +51,7 @@ | |
| <br><a href="/FAQ.html">FAQ</a> | |
| <br><a href="/cvs_anon.html">Accessing CVS</a> | |
| <br><a href="/cgi-bin/cvsweb/busybox/">Browse CVS</a> | |
| + | <br><a href="http://bugs.busybox.net/">Bug Tracking</a> |
| <br><a href="/docs.html">Documentation</a> | |
| <br><a href="/products.html">Products</a> | |
| <br><a href="/shame.html">Hall of Shame</a> | |
docs/busybox.net/news.html+19 -0
| @@ -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 | |