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

English fixes #29336

Merged
merged 1 commit into from
Oct 4, 2018
Merged

English fixes #29336

merged 1 commit into from
Oct 4, 2018

Conversation

mark-summerfield
Copy link
Contributor

I did not change "i.e." to "i.e.," even though I think the latter is better since the former seems to be your standard.

I find the package name 'Priv' v. confusing esp. in contexts like "The public Priv" etc. I think Util would be a more plausible and less
confusing example name. (I also think 'Pub' ought to be replaced by a more plausible name, e.g., 'Process' or 'Compute'.)

I find it confusing that the text mentions the "/home/me/animals" directory, but then shows a dictionary using "/home/me/AnimalPackages".

PS I tried doing this from a local git clone but when I did the git push it gave me a 403.
I did git clone ...julia.git, the cd'd into julia, then did git checkout -b english_fixes, then made my changes and did git commit -a, put in the comments above, then did git push --set-upstream origin english_fixes, entered my git username and password -- and then got the 403. I can carry on using the web interface though, but then you'll end up with lots of small commits -- but maybe you prefer than anyway.

I did not change "i.e." to "i.e.," even though I think the latter is better since the former seems to be your standard.

I find the package name 'Priv' v. confusing esp. in contexts like "The public `Priv`" etc. I think Util would be a more plausible and less
confusing example name. (I also think 'Pub' ought to be replaced by a more plausible name, e.g., 'Process' or 'Compute'.)

I find it confusing that the text mentions the "/home/me/animals" directory, but then shows a dictionary using "/home/me/AnimalPackages".

PS I tried doing this from a local git clone but when I did the git push it gave me a 403.
I did git clone ...julia.git, the cd'd into julia, then did git checkout -b english_fixes, then made my changes and did git commit -a, put in the comments above, then did git push --set-upstream origin english_fixes, entered my git username and password -- and then got the 403. I can carry on using the web interface though.
@fredrikekre fredrikekre added the docs This change adds or pertains to documentation label Sep 24, 2018
Copy link
Sponsor Member

@StefanKarpinski StefanKarpinski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bit more opinionated than a simple English fixes edit, but it seems to be a positive change on the whole.

@fredrikekre
Copy link
Member

PS I tried doing this from a local git clone but when I did the git push it gave me a 403.
I did git clone ...julia.git, the cd'd into julia, then did git checkout -b english_fixes, then made my changes and did git commit -a, put in the comments above, then did git push --set-upstream origin english_fixes, entered my git username and password -- and then got the 403. I can carry on using the web interface though, but then you'll end up with lots of small commits -- but maybe you prefer than anyway.

You probably need to add your fork as a remote, since you can not push to the JuliaLang/julia repo.

@JeffBezanson JeffBezanson merged commit 7dd1e4c into JuliaLang:master Oct 4, 2018
@mark-summerfield mark-summerfield deleted the patch-6 branch October 4, 2018 08:12
KristofferC pushed a commit that referenced this pull request Oct 6, 2018
(cherry picked from commit 7dd1e4c)
KristofferC pushed a commit that referenced this pull request Feb 11, 2019
(cherry picked from commit 7dd1e4c)
KristofferC pushed a commit that referenced this pull request Feb 20, 2020
(cherry picked from commit 7dd1e4c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change adds or pertains to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants