Re: [PATCH 2/2] Split bash compatible extensions into separate options.

2017-01-11 Thread Denys Vlasenko
On Wed, Jan 11, 2017 at 12:32 PM, Kang-Che Sung wrote: > On Wed, Jan 11, 2017 at 4:09 PM, Denys Vlasenko > wrote: >> On Tue, Jan 10, 2017 at 8:17 PM, Kang-Che Sung wrote: >>> All of the bash compatibility options will now

Re: [PATCH 2/2] Split bash compatible extensions into separate options.

2017-01-11 Thread Kang-Che Sung
On Wed, Jan 11, 2017 at 4:09 PM, Denys Vlasenko wrote: > On Tue, Jan 10, 2017 at 8:17 PM, Kang-Che Sung wrote: >> All of the bash compatibility options will now depend on >> CONFIG_*_BASH_COMPAT, and CONFIG_*_BASH_COMPAT become an option that >>

Re: [PATCH 2/2] Split bash compatible extensions into separate options.

2017-01-11 Thread Denys Vlasenko
On Tue, Jan 10, 2017 at 8:17 PM, Kang-Che Sung wrote: > All of the bash compatibility options will now depend on > CONFIG_*_BASH_COMPAT, and CONFIG_*_BASH_COMPAT become an option that > alone doesn't add any code. > > Splitting these options allows more flexibility in

Re: [PATCH 2/2] Split bash compatible extensions into separate options.

2017-01-10 Thread Kang-Che Sung
On Wed, Jan 11, 2017 at 3:17 AM, Kang-Che Sung wrote: > (Note: this is a large patch. Patch included as mail attachment) > > All of the bash compatibility options will now depend on > CONFIG_*_BASH_COMPAT, and CONFIG_*_BASH_COMPAT become an option that > alone doesn't add

[PATCH 2/2] Split bash compatible extensions into separate options.

2017-01-10 Thread Kang-Che Sung
files changed, 239 insertions(+), 118 deletions(-) From 655b1f7dd97c83c79502a0635fe9d195de47beaa Mon Sep 17 00:00:00 2001 From: Kang-Che Sung <explore...@gmail.com> Date: Wed, 11 Jan 2017 03:02:24 +0800 Subject: [PATCH 2/2] Split bash compatible extensions into separate options. All