Mention the behavior if user selects CONFIG_SH_IS_ASH but not
CONFIG_ASH. We will be explicit that invocations like "busybox ash"
will not work for such configuration.
Also clarify help text of CONFIG_BASH_IS_* that bash compatibility in
ash is not complete. (It shouldn't be anyway - ash can't sup
(This mail and patch was sent to busybox mailing list on Dec 25, 2016,
and I'm re-sending again for people to notice.)
Mention the behavior if user selects CONFIG_SH_IS_ASH but not
CONFIG_ASH. We will be explicit that invocations like "busybox ash"
will not work for such configuration.
Also clari
Applied, thanks!
On Wed, Jan 4, 2017 at 1:57 AM, Kang-Che Sung wrote:
> (This mail and patch was sent to busybox mailing list on Dec 25, 2016,
> and I'm re-sending again for people to notice.)
>
> Mention the behavior if user selects CONFIG_SH_IS_ASH but not
> CONFIG_ASH. We will be explicit that