[git commit master 1/1] FAQ.html: remove part about firmware upload

Denys Vlasenko vda.linux at googlemail.com
Tue Mar 8 10:26:12 UTC 2011

commit: http://git.busybox.net/busybox-website/commit/?id=0eb73cfe9af2b71f0476aabc632a851eb0b19afe
branch: http://git.busybox.net/busybox-website/commit/?id=refs/heads/master

Signed-off-by: Denys Vlasenko <vda.linux at googlemail.com>
 FAQ.html |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/FAQ.html b/FAQ.html
index 19a65bd..d5f5376 100644
--- a/FAQ.html
+++ b/FAQ.html
@@ -608,8 +608,7 @@ binary firmware images.
 If you want to be extra nice, you may provide URLs to places
 where people may get ARM toolchains or read HOWTOs explaining
 how to build one. You may even provide the toolchain.
-You may explain how to download newly built Busybox binary
-into the device. But these "extra nice" things are not required
+But these "extra nice" things are not required
 by license. License also does not require you to provide
 any support for users which use firmware (or part of it)
 built from source.
@@ -618,7 +617,8 @@ What license does require, though, is that Busybox
 source which you provide actually can be built and that
 it will match Busybox binary which is found in your binary firmware.
 Match is meant as "functional match", not byte-by-byte match -
-binaries may slightly differ because of different compilers/linkers used.
+binaries may slightly differ because of different compilers/linkers used,
+because of build timestamp and so on.
 <hr />

More information about the busybox-cvs mailing list