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

parse_env should be something else? #549

Closed
00vareladavid opened this issue Jul 31, 2018 · 0 comments · Fixed by #599
Closed

parse_env should be something else? #549

00vareladavid opened this issue Jul 31, 2018 · 0 comments · Fixed by #599

Comments

@00vareladavid
Copy link
Contributor

It is here now.
It was here before #509. But I can't find any reference to it?

bors bot added a commit that referenced this issue Aug 13, 2018
599: Remove `--env` meta option r=KristofferC a=00vareladavid

Should close #590 and close #549

618: better info messages for activating new env r=KristofferC a=fredrikekre



Co-authored-by: David Varela <00.varela.david@gmail.com>
Co-authored-by: Fredrik Ekre <fredrik.ekre@chalmers.se>
bors bot added a commit that referenced this issue Aug 13, 2018
599: Remove `--env` meta option r=KristofferC a=00vareladavid

Should close #590 and close #549

618: better info messages for activating new env r=KristofferC a=fredrikekre



Co-authored-by: David Varela <00.varela.david@gmail.com>
Co-authored-by: Fredrik Ekre <fredrik.ekre@chalmers.se>
@bors bors bot closed this as completed in #599 Aug 13, 2018
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 a pull request may close this issue.

1 participant