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

friendlier error message (Improve error message for bad build targets #2384) #2850

Merged
merged 1 commit into from
Jan 6, 2017

Conversation

bar9
Copy link

@bar9 bar9 commented Dec 15, 2016

#2384
Changes:

  • Friendlier error message
    Tested:
  • We ran the example provided in the issue

@bar9 bar9 changed the title friendlier error message (Improve error message for bad build targets #2384) friendlier error message (Improve error message for bad build targets #2384) https://github.com/commercialhaskell/stack/pull/2850 Dec 22, 2016
@bar9 bar9 changed the title friendlier error message (Improve error message for bad build targets #2384) https://github.com/commercialhaskell/stack/pull/2850 friendlier error message (Improve error message for bad build targets #2384) https://github.com/commercialhaskell/stack/issues/2384 Dec 22, 2016
@bar9 bar9 changed the title friendlier error message (Improve error message for bad build targets #2384) https://github.com/commercialhaskell/stack/issues/2384 friendlier error message (Improve error message for bad build targets #2384) Dec 22, 2016
@snoyberg
Copy link
Contributor

snoyberg commented Jan 2, 2017

This looks good. Could you put a comment in the ChangeLog about the improved wording?

@sphaso
Copy link
Contributor

sphaso commented Jan 5, 2017

@snoyberg absolutely. We amended the commit with a small comment in the ChangeLog.

@mgsloan
Copy link
Contributor

mgsloan commented Jan 6, 2017

LGTM!

@mgsloan mgsloan merged commit ca3b70d into commercialhaskell:master Jan 6, 2017
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.

4 participants