-
Notifications
You must be signed in to change notification settings - Fork 35
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
Update prose in page to indicate hardware and software requirements. #26
Comments
Please merge this with #18 to keep all README related issues in a single place. |
Brings up a discussion of what goes on readme developer side vs page client
side
…On Thu., Dec. 5, 2019, 1:02 p.m. Kory, ***@***.***> wrote:
Please merge this with #18 <#18>
to keep all README related issues in a single place.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#26?email_source=notifications&email_token=AA36GFOKUTWJXYS4T6TRS3LQXFM3VA5CNFSM4JV7JI3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGB6XAY#issuecomment-562293635>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA36GFOTBN5KQ7BJB4ZKVSDQXFM3VANCNFSM4JV7JI3A>
.
|
Agree to disagree. I think all discussion around shaping a README.md file should take place in a single issue. |
This issue is about client side instructions outside the readme ?
…On Thu., Dec. 5, 2019, 1:06 p.m. Kory, ***@***.***> wrote:
Agree to disagree. I think all discussion around shaping a README.md file
should take place in a single issue.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#26?email_source=notifications&email_token=AA36GFO3KNUKYUDRCIMVX5LQXFNOBA5CNFSM4JV7JI3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGB7F3I#issuecomment-562295533>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA36GFNAOQRC6B3EDRRKJK3QXFNOBANCNFSM4JV7JI3A>
.
|
So client side text should be the focus of this issue? Fixed title to reflect. |
korymath
changed the title
Update prose in page and readme to indicate hardware and software requirements
Update prose in page to indicate hardware and software requirements.
Dec 5, 2019
Yes exactly what does.mom.need to know when we send her the link
…On Thu., Dec. 5, 2019, 1:17 p.m. Kory, ***@***.***> wrote:
So client side text should be the focus of this issue?
Fixed title to reflect.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#26?email_source=notifications&email_token=AA36GFINTK6JA2UZ2NIE2H3QXFOXPA5CNFSM4JV7JI3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGCAHEQ#issuecomment-562299794>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA36GFM5AJNETPBWMUYUKHDQXFOXPANCNFSM4JV7JI3A>
.
|
done in update to master accidently after making branch and not checking it out |
No worries. Thanks yo! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Chrome
OSX
Muse 1 2016
Muse 2
The text was updated successfully, but these errors were encountered: