Kill CONFIG_NITPICK, it turned out to not be useful. no code changes.

1 files changed, 0 insertions, 18 deletions

diff --git a/Config.in b/Config.in
index a3354eb59..5ce642ff3 100644
--- a/Config.in
+++ b/Config.in
@@ -13,22 +13,6 @@ menu "Busybox Settings"
 
 menu "General Configuration"
 
-config NITPICK
-        bool "See lots more (probably unnecessary) configuration options."
-        default n
-        help
-          Some BusyBox applets have more configuration options than anyone
-          will ever care about.  To avoid drowining people in complexity, most
-          of the applet features that can be set to a sane default value are
-          hidden, unless you hit the above switch.
-
-          This is better than to telling people to edit the busybox source
-          code, but not by much.
-
-          See http://en.wikipedia.org/wiki/Fibber_McGee_and_Molly#The_Closet
-
-          You have been warned.
-
 config DESKTOP
         bool "Enable options for full-blown desktop systems"
         default n
@@ -40,7 +24,6 @@ config DESKTOP
 choice
         prompt "Buffer allocation policy"
         default FEATURE_BUFFERS_USE_MALLOC
-        depends on NITPICK
         help
           There are 3 ways BusyBox can handle buffer allocations:
           - Use malloc. This costs code size for the call to xmalloc.
@@ -130,7 +113,6 @@ config FEATURE_DEVPTS
 config FEATURE_CLEAN_UP
         bool "Clean up all memory before exiting (usually not needed)"
         default n
-        depends on NITPICK
         help
           As a size optimization, busybox normally exits without explicitly
           freeing dynamically allocated memory or closing files.  This saves