http://busybox.net/developer.html
The developers also have a bug and patch tracking system
- (http://bugs.busybox.net) although posting a bug/patch to the mailing list
+ (https://bugs.busybox.net) although posting a bug/patch to the mailing list
is generally a faster way of getting it fixed, and the complete archive of
what happened is the subversion changelog.
only so much they can keep in their brains at a time. You can post a
polite reminder after 2-3 days without offending anybody. If that doesn't
result in a solution, please use the
- <a href="http://bugs.busybox.net/">BusyBox Bug
+ <a href="https://bugs.busybox.net/">BusyBox Bug
and Patch Tracking System</a> to submit a detailed explanation and we'll
get to it as soon as we can.
</p>
<li><a href="subversion.html">Source Control</a></li>
<!--li><a href="/downloads/patches/recent.html">Recent Changes</a></li-->
<li><a href="lists.html">Mailing Lists</a></li>
- <li><a href="http://bugs.busybox.net/">Bug Tracking</a></li>
+ <li><a href="https://bugs.busybox.net/">Bug Tracking</a></li>
</ul>
<p><b>Links</b>
<ul>
several existing applets. This prerelease should be noticeably more
<a href="http://www.opengroup.org/onlinepubs/009695399/">standards
compliant</a> than earlier versions of busybox, although we're
- still working out the <a href="http://bugs.busybox.net">bugs</a>.</p>
+ still working out the <a href="https://bugs.busybox.net">bugs</a>.</p>
<li><b>16 August 2005 -- 1.01 is out</b>
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>
+ <a href="https://bugs.busybox.net/">shiny new Bug and Patch Tracking System</a>
to post all the gory details.
<p>