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

Clarify activate command signatures #2037

Merged
merged 1 commit into from Mar 25, 2021

Conversation

danielmatz
Copy link
Contributor

The signatures in the help for the activate command were confusing. It seemed to imply that the activate --shared and activate --temp each took an optional path, when in fact activate --shared requires a path and activate --temp does not accept a path. This clarifies the command signatures for these two cases.

The signatures in the help for the activate command were confusing. It seemed to imply that the `activate --shared` and `activate --temp` each took an optional path, when in fact `activate --shared` requires a path and `activate --temp` does not accept a path. This clarifies the command signatures for these two cases.
@StefanKarpinski
Copy link
Sponsor Member

I restarted the doc build; the macOS Travis failures are unrelated (due to PCRE upgrade).

@00vareladavid
Copy link
Contributor

Is the best way to restart tests still to close then open the PR?

@00vareladavid
Copy link
Contributor

I'm merging because macOS tests are all green, not sure why this is still pointing to Travis tests (seems we do not use it at all anymore)

@00vareladavid 00vareladavid merged commit c80be62 into JuliaLang:master Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants