24c20b1d1
Eric Andersen
2004-07-20
Subject
more doc updates
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
docs/busybox.net/news.html+13 -1
| @@ -12,7 +12,19 @@ | |
| I <b>really</b> want to get BusyBox 1.0.0 released soon and I see no reason | |
| real reason why the 1.0.0 release shouldn't happen with things pretty much as is. | |
| - | Remember, please do not bother to send in patches adding cool new features |
| + | |
| + | I <b>really</b> want to get BusyBox 1.0.0 released soon and I see no real |
| + | reason why the 1.0.0 release shouldn't happen with things pretty much as |
| + | is. BusyBox is in good shape at the moment, and it works nicely for |
| + | everything that I'm doing with it. And from the reports I've been getting, |
| + | it works nicely for what most everyone else is doing with it as well. |
| + | There will eventually be a 1.0.1 anyway, so we might as well get on with |
| + | it. No BusyBox is not perfect. No piece of software ever is. And while |
| + | there is still plenty that can be done to improve things, most of that work |
| + | is waiting till we can get a solid 1.0.0 release out the door.... |
| + | <p> |
| + | |
| + | Please do not bother to send in patches adding cool new features |
| at this time. Only bug-fix patches will be accepted. It would also be | |
| <b>very</b> helpful if people could continue to review the BusyBox | |
| documentation and submit improvements. | |