- add note pointing to the stable branch, so users can pickup the current

  stable version with fixes via svn.

diff --git a/docs/busybox.net/news.html b/docs/busybox.net/news.html
index a5a36e9ccb4c4673dfa9a16436177cd3b2201d4f..2f703e64c0f4d1323c35f0b31de26835e72377d0 100644 (file)
--- a/docs/busybox.net/news.html
+++ b/docs/busybox.net/news.html
@@ -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

diff --git a/docs/busybox.net/subversion.html b/docs/busybox.net/subversion.html
index 65be61c73cc190f882ed9b06ab125e215bf7bf6d..fb4bac77475e043be6e8c1a9a08956e30692da28 100644 (file)
--- a/docs/busybox.net/subversion.html
+++ b/docs/busybox.net/subversion.html
@@ -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