Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove check of max_depth #838

Merged
merged 2 commits into from
Aug 16, 2017

Conversation

henry0312
Copy link
Contributor

max_depth can take both positive and negative value

guolinke and others added 2 commits August 16, 2017 13:36
max_depth can take both positive and negative value
@henry0312
Copy link
Contributor Author

henry0312 commented Aug 16, 2017

I think we should not push to master brach directory, we should check of passing tests.
50534f1

@henry0312 henry0312 deleted the remove_check_max_depth branch August 16, 2017 05:52
@guolinke
Copy link
Collaborator

@henry0312 I just want to fix it forcefully, but find your PR.
So I merge it directly.

@henry0312
Copy link
Contributor Author

Okay, I see :)

guolinke pushed a commit that referenced this pull request Aug 16, 2017
* output warning when only set `max_depth`

* Remove check of max_depth

max_depth can take both positive and negative value
guolinke pushed a commit that referenced this pull request Aug 18, 2017
* output warning when only set `max_depth`

* Remove check of max_depth

max_depth can take both positive and negative value
guolinke pushed a commit that referenced this pull request Oct 9, 2017
* output warning when only set `max_depth`

* Remove check of max_depth

max_depth can take both positive and negative value
@lock lock bot locked as resolved and limited conversation to collaborators Mar 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants