aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMark Whitley <markw@lineo.com>2001-03-02 19:15:01 +0000
committerMark Whitley <markw@lineo.com>2001-03-02 19:15:01 +0000
commit42ab250709099a1ba6c42e324f828d2a767bae86 (patch)
tree87ec8b192cc1957e9605308fa73896438ec68df5 /docs
parent3b565cdf910a95e0955d3480fcd617fa5dbda78b (diff)
downloadbusybox-42ab250709099a1ba6c42e324f828d2a767bae86.tar.gz
Removed section on testing that is now in contributing.txt.
Diffstat (limited to 'docs')
-rw-r--r--docs/style-guide.txt20
1 files changed, 0 insertions, 20 deletions
diff --git a/docs/style-guide.txt b/docs/style-guide.txt
index ddf3ebb83..1f06662ac 100644
--- a/docs/style-guide.txt
+++ b/docs/style-guide.txt
@@ -607,23 +607,3 @@ illustrates emphasizing logical blocks:
/* clean up */
free(line);
}
-
-
-Testing Guidelines
-~~~~~~~~~~~~~~~~~~
-
-It's considered good form to test your new feature before you submit a patch
-to the mailing list, and especially before you commit a change to CVS. Here
-are some guidelines on testing your changes.
-
- - Always test busybox applets against GNU counterparts and make sure the
- behavior / output is identical between the two.
-
- - Try several different permutations and combinations of the features you're
- adding and make sure they all work. (Make sure one feature does not
- interfere with another, etc.)
-
- - Make sure you test compiling against the source both with the feature
- turned on and turned off in Config.h and make sure busybox compiles cleanly
- both ways.
-