66 |
|
|
67 |
You can browse the up to the minute source code and change history online. |
You can browse the up to the minute source code and change history online. |
68 |
|
|
69 |
http://www.busybox.net/cgi-bin/viewcvs.cgi/trunk/busybox/ |
http://git.busybox.net/busybox/ |
70 |
|
|
71 |
Anonymous GIT access is available. For instructions, check out: |
Anonymous GIT access is available. For instructions, check out: |
72 |
|
|
83 |
what happened is the subversion changelog. |
what happened is the subversion changelog. |
84 |
|
|
85 |
Note: if you want to compile busybox in a busybox environment you must |
Note: if you want to compile busybox in a busybox environment you must |
86 |
select ENABLE_DESKTOP. |
select CONFIG_DESKTOP. |
87 |
|
|
88 |
---------------- |
---------------- |
89 |
|
|
90 |
getting help: |
Getting help: |
91 |
|
|
92 |
when you find you need help, you can check out the busybox mailing list |
when you find you need help, you can check out the busybox mailing list |
93 |
archives at http://busybox.net/lists/busybox/ or even join |
archives at http://busybox.net/lists/busybox/ or even join |
95 |
|
|
96 |
---------------- |
---------------- |
97 |
|
|
98 |
bugs: |
Bugs: |
99 |
|
|
100 |
if you find bugs, please submit a detailed bug report to the busybox mailing |
if you find bugs, please submit a detailed bug report to the busybox mailing |
101 |
list at busybox@busybox.net. a well-written bug report should include a |
list at busybox@busybox.net. a well-written bug report should include a |
194 |
---------------- |
---------------- |
195 |
|
|
196 |
Please feed suggestions, bug reports, insults, and bribes back to the busybox |
Please feed suggestions, bug reports, insults, and bribes back to the busybox |
197 |
maintainer: |
mailing list: |
198 |
|
|
199 |
|
busybox@busybox.net |
200 |
|
|
201 |
|
and/or maintainer: |
202 |
|
|
203 |
Denys Vlasenko |
Denys Vlasenko |
204 |
<vda.linux@googlemail.com> |
<vda.linux@googlemail.com> |