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

Use --warning-* instead of --warn-* #88

Merged
merged 2 commits into from Apr 19, 2016

Conversation

a-know
Copy link
Contributor

@a-know a-know commented Mar 16, 2016

relate with #87 (comment)

@Songmu intend to use --warning-under --warning-over, but implementation is not.
This is the pull request to amend that implementation.

@a-know
Copy link
Contributor Author

a-know commented Mar 16, 2016

I worried about amend go-check-plugins/check-procs or not.
(go-check-plugins/check-procs used --warn-*, too. https://github.com/mackerelio/go-check-plugins/blob/master/check-procs/check_procs.go#L15)

If it is better to fix go-check-plugins/check-procs, I can also fix that in this PR.

@Songmu
Copy link
Contributor

Songmu commented Apr 19, 2016

Sorry for slow response.
I refine this patch for maintaining backward compatibility at #104.

Thank you!

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.

None yet

2 participants