diff options
author | Eric Andersen <andersen@codepoet.org> | 2005-01-31 13:05:02 +0000 |
---|---|---|
committer | Eric Andersen <andersen@codepoet.org> | 2005-01-31 13:05:02 +0000 |
commit | ff4b924d2044556d90ae70b902882807b9c0b8cf (patch) | |
tree | 5ca5e22bf85002aa55f62adaa415df633158fb69 /docs/busybox.net | |
parent | 16b8579f530add389e670cbec3a5dad09fcc3668 (diff) | |
download | busybox-w32-ff4b924d2044556d90ae70b902882807b9c0b8cf.tar.gz busybox-w32-ff4b924d2044556d90ae70b902882807b9c0b8cf.tar.bz2 busybox-w32-ff4b924d2044556d90ae70b902882807b9c0b8cf.zip |
Update the bug submission stuff to point to bugs.busybox.net
Diffstat (limited to 'docs/busybox.net')
-rw-r--r-- | docs/busybox.net/FAQ.html | 56 |
1 files changed, 20 insertions, 36 deletions
diff --git a/docs/busybox.net/FAQ.html b/docs/busybox.net/FAQ.html index 0f5f08890..b70c03a82 100644 --- a/docs/busybox.net/FAQ.html +++ b/docs/busybox.net/FAQ.html | |||
@@ -85,49 +85,33 @@ have additions to this FAQ document, we would love to add them, | |||
85 | <h2><a name="bugs">I think I found a bug in BusyBox! What should I do?</h2> | 85 | <h2><a name="bugs">I think I found a bug in BusyBox! What should I do?</h2> |
86 | <p> | 86 | <p> |
87 | 87 | ||
88 | If you find a problem with BusyBox, please submit a detailed bug report to | ||
89 | the BusyBox mailing list at <a href="mailto:busybox@mail.busybox.net"> | ||
90 | busybox@mail.busybox.net</a>. Please do not send private email to Erik | ||
91 | (the maintainer of BusyBox) asking for private help unless you are planning | ||
92 | on paying for consulting services. When we answer questions on the BusyBox | ||
93 | mailing list, it helps everyone, while private answers help only you... | ||
94 | 88 | ||
95 | <p> | 89 | <p> |
96 | |||
97 | If you find bugs, please submit a detailed bug report to the BusyBox mailing | ||
98 | list at busybox@mail.busybox.net. A well-written bug report should include a | ||
99 | transcript of a shell session that demonstrates the bad behavior and enables | ||
100 | anyone else to duplicate the bug on their own machine. The following is such | ||
101 | an example: | ||
102 | |||
103 | <pre> | ||
104 | To: busybox@mail.busybox.net | ||
105 | From: diligent@testing.linux.org | ||
106 | Subject: /bin/date doesn't work | ||
107 | |||
108 | Package: BusyBox | ||
109 | Version: 1.00 | ||
110 | |||
111 | When I execute BusyBox 'date' it produces unexpected results. | ||
112 | With GNU date I get the following output: | ||
113 | 90 | ||
114 | $ date | 91 | If you simply need help with using or configuring BusyBox, please submit a |
115 | Fri Oct 8 14:19:41 MDT 2004 | 92 | detailed description of your problem to the BusyBox mailing list at <a |
93 | href="mailto:busybox@mail.busybox.net"> busybox@mail.busybox.net</a>. | ||
94 | Please do not send private email to Erik (the maintainer of BusyBox) asking | ||
95 | for private help unless you are planning on paying for consulting services. | ||
96 | When we answer questions on the BusyBox mailing list, it helps everyone, | ||
97 | while private answers help only you... | ||
116 | 98 | ||
117 | But when I use BusyBox date I get this instead: | 99 | <p> |
118 | 100 | ||
119 | $ date | 101 | The developers of BusyBox are busy people, and have only so much they can |
120 | illegal instruction | 102 | keep in their brains at a time. As a result, bug reports sometimes get |
103 | lost when posted to the mailing list. To prevent your bug report from | ||
104 | getting lost, if you find a bug in BusyBox, please use the <a | ||
105 | href="http://bugs.busybox.net/">BusyBox Bug and Patch Tracking System</a> | ||
106 | to submit a detailed bug report. | ||
121 | 107 | ||
122 | I am using Debian unstable, kernel version 2.4.27 on a x86 system, | 108 | <p> |
123 | and the latest uClibc from CVS. Thanks for the wonderful program! | ||
124 | 109 | ||
125 | -Diligent | 110 | The same also applies to patches... Regardless of whether your patch is a |
126 | </pre> | 111 | bug fix or adds shiney new features, please post your patch to the <a |
112 | href="http://bugs.busybox.net/">BusyBox Bug and Patch Tracking System</a> | ||
113 | to make certain it is properly considered. | ||
127 | 114 | ||
128 | Note the careful description and use of examples showing not only what BusyBox | ||
129 | does, but also a counter example showing what an equivalent GNU app does. Bug | ||
130 | reports lacking proper detail may never be fixed... Thanks for understanding. | ||
131 | 115 | ||
132 | <hr /> | 116 | <hr /> |
133 | <p> | 117 | <p> |