diff options
| author | Denys Vlasenko <vda.linux@googlemail.com> | 2017-07-27 02:59:13 +0200 |
|---|---|---|
| committer | Denys Vlasenko <vda.linux@googlemail.com> | 2017-07-27 02:59:13 +0200 |
| commit | 86d5bf4246a7ba68d220bc6c7a7a3be62119dc12 (patch) | |
| tree | 7673ca6a045e66ef64581b7193054b8c763d5b69 /libbb | |
| parent | 488e609203c23b9826f75179f1b8e567617138ae (diff) | |
| download | busybox-86d5bf4246a7ba68d220bc6c7a7a3be62119dc12.tar.gz | |
config: trim/improve item names and help texts.
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'libbb')
| -rw-r--r-- | libbb/Config.src | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/libbb/Config.src b/libbb/Config.src index 9da8b65ee..3c1b064b6 100644 --- a/libbb/Config.src +++ b/libbb/Config.src @@ -11,14 +11,13 @@ choice prompt "Buffer allocation policy" default FEATURE_BUFFERS_USE_MALLOC help - There are 3 ways BusyBox can handle buffer allocations: + There are 3 ways busybox can handle buffer allocations: - Use malloc. This costs code size for the call to xmalloc. - Put them on stack. For some very small machines with limited stack space, this can be deadly. For most folks, this works just fine. - Put them in BSS. This works beautifully for computers with a real MMU (and OS support), but wastes runtime RAM for uCLinux. This - behavior was the only one available for BusyBox versions 0.48 and - earlier. + behavior was the only one available for versions 0.48 and earlier. config FEATURE_BUFFERS_USE_MALLOC bool "Allocate with Malloc" |