Skip to content

[5.x] [optimizer] use "unsafe" defaults that have proven to be safe enough#10380

Merged
spalger merged 1 commit into5.xfrom
jasper/backport/10275/5.x
Feb 16, 2017
Merged

[5.x] [optimizer] use "unsafe" defaults that have proven to be safe enough#10380
spalger merged 1 commit into5.xfrom
jasper/backport/10275/5.x

Conversation

@elastic-jasper
Copy link
Copy Markdown
Contributor

[optimizer] use "unsafe" defaults that have proven to be safe enough

Backports PR #10275

Commit 1:
[optimizer] use "unsafe" defaults that have proven to be safe enough

Commit 2:
[docs] add a note to the CONTRIBUTING.md regarding potential pitfalls

Backports PR #10275

**Commit 1:**
[optimizer] use "unsafe" defaults that have proven to be safe enough

* Original sha: 045d624
* Authored by spalger <spalger@users.noreply.github.com> on 2017-02-09T20:52:32Z

**Commit 2:**
[docs] add a note to the CONTRIBUTING.md regarding potential pitfalls

* Original sha: 68be975
* Authored by spalger <spalger@users.noreply.github.com> on 2017-02-14T18:43:39Z
@elastic-jasper elastic-jasper added the backport This PR is a backport of another PR label Feb 15, 2017
@spalger spalger merged commit 868e886 into 5.x Feb 16, 2017
@epixa epixa deleted the jasper/backport/10275/5.x branch February 28, 2017 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants