- add note pointing to the stable branch, so users can pickup the current stable version with fixes via svn.
This commit was genuinely broken at the time (not related to our build system): scripts/config/mkconfigs.c (2005-08-01 - 2006-10-05 arasi) uretilen bbconfigopts.h icine .config satirlarini kacissiz, ham newline'larla gömüyordu - gecerli C degildi, busybox'un kendi bb_mkdep araci bile parse edemiyordu (7d219aab7 ile duzeltildi, mkconfigs shell scripte cevrildi)
No binary (build failed)
—
(log yok)
| @@ -9,6 +9,11 @@ | |
| find -xdev, and a fix for comm. Check the file "changelog" in the tarball | |
| for more info.</p> | |
| + | <p>You can obtain the current stable branch via |
| + | <pre> |
| + | svn co svn://busybox.net/branches/busybox_1_1_stable |
| + | </pre></p> |
| + | |
| <p>The next new development release (1.2.0) is slated for June. A 1.1.3 | |
| will be released before then if more bug fixes crop up. (The new plan is | |
| to have a 1.x.0 new development release every 3 months, with 1.x.y stable | |
| @@ -18,7 +18,13 @@ grab a copy of the latest version of BusyBox using anonymous svn access: | |
| <pre> | |
| svn co svn://busybox.net/trunk/busybox</pre> | |
| + | <p> |
| + | The current <em>stable branch</em> can be obtained with |
| + | <pre> |
| + | svn co svn://busybox.net/branches/busybox_1_1_stable |
| + | </pre> |
| + | </p> |
| <p> | |
| If you are not already familiar with using Subversion, I recommend you visit <a | |