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 warn_error from default tags #521

Merged
merged 1 commit into from
Mar 20, 2016
Merged

Remove warn_error from default tags #521

merged 1 commit into from
Mar 20, 2016

Conversation

ansiwen
Copy link
Contributor

@ansiwen ansiwen commented Mar 20, 2016

Adding warn_error to the default tags for warnings that have been
enabled in the same step is a regression, since there has been no
inermediate period where this warnings could have been fixed. This
change removes the warn_error tag from the default tags.

Fixes: #520

Adding warn_error to the default tags for warnings that have been
enabled in the same step is a regression, since there has been no
inermediate period where this warnings could have been fixed.  This
change removes the warn_error tag from the default tags.

Fixes: #520
samoht added a commit that referenced this pull request Mar 20, 2016
Remove warn_error from default tags
@samoht samoht merged commit af85b65 into mirage:master Mar 20, 2016
@samoht
Copy link
Member

samoht commented Mar 20, 2016

Ok, I'll merge this and add a new flag --warn-error to turn on/off that behaviour. The default behaviour will be the same as it was for 2.7.0.

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.

Changing default tags to contain strict 'warn_error(+1..49)' breaks builds
2 participants