这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@michaelshobbs
Copy link
Member

My thinking here is if we’re going to have a baseline bash version requirement, then we should have a damn good reason for it. Currently, there is no real need to support bash>=4.3; especially not for just one line of code.

Given that this PR is so small and still maintains bash<4.3 support, I think it’s reasonable to maintain that support for now. If we end up finding ourselves having to go through uncomfortable machinations to support bash>=4.2, then we punt and force the bash>=4.3 requirement.

@michaelshobbs
Copy link
Member Author

/cc @u2mejc @josegonzalez

@josegonzalez
Copy link
Member

Closing, this is no longer necessary since i just updated all the envs...

@josegonzalez josegonzalez deleted the mh-support-bash-4.2 branch January 18, 2016 02:43
@josegonzalez josegonzalez restored the mh-support-bash-4.2 branch January 18, 2016 02:48
@josegonzalez josegonzalez reopened this Jan 18, 2016
michaelshobbs added a commit that referenced this pull request Jan 18, 2016
support bash 4.2 so we don't have to modify all plugin test envs
@michaelshobbs michaelshobbs merged commit 71351f1 into master Jan 18, 2016
@josegonzalez josegonzalez deleted the mh-support-bash-4.2 branch January 18, 2016 06:50
@josegonzalez josegonzalez changed the title support bash 4.2 so we don't have to modify all plugin test envs Support bash 4.2 so we don't have to modify all plugin test envs Jan 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants