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

Fix typo. #6

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix typo. #6

wants to merge 2 commits into from

Conversation

naviji
Copy link

@naviji naviji commented Feb 17, 2021

No description provided.

@ajdlinux
Copy link
Owner

Thanks for the PR.

@daxtens I think you wrote this, and I don't think this is a typo but perhaps it could be phrased more clearly?

@daxtens
Copy link
Collaborator

daxtens commented Feb 17, 2021 via email

@naviji
Copy link
Author

naviji commented Feb 18, 2021

I've split the sentence into two.

@daxtens
Copy link
Collaborator

daxtens commented Feb 24, 2021

That's fine with me.

@valerio-bozzolan
Copy link

I don't know why I'm here but I just noticed that it makes sense to merge.

@@ -73,7 +73,7 @@ You can check that your email has been received by checking the mailing list arc

Then, you keep waiting. Three things may happen:

* You might get a response to your email. Often these will be comments, which may require you to make changes to your patch, or explain why your way is the best way. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.
* You might get a response to your email. Often these will be comments, which may require you to make changes to your patch. You might be asked to explain why your way is the best. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.

Choose a reason for hiding this comment

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

Suggested change
* You might get a response to your email. Often these will be comments, which may require you to make changes to your patch. You might be asked to explain why your way is the best. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.
* You might get a response to your email. Often these will be comments, which may require you to make changes to your patch. You also might be asked to explain why your way is the best. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.

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.

5 participants