tions(+), 118 deletions(-)
From 655b1f7dd97c83c79502a0635fe9d195de47beaa Mon Sep 17 00:00:00 2001
From: Kang-Che Sung
Date: Wed, 11 Jan 2017 03:02:24 +0800
Subject: [PATCH 2/2] Split bash compatible extensions into separate options.
All of the bash compatibility options will now depend on
CO
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 any code.
>
> Splitting t
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 configuration
Configuration
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
>> alone doesn't add any code.
>>
>> Splitting these o
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 depend on
>>> CONFIG_*_BASH_COMPAT, and CONFIG_*_BASH_COMPAT become an opt