Readme++#47
Open
slipher wants to merge 3 commits into
Open
Conversation
Member
|
If you push this to my branch it would be easier, as I also have things to write more above your changes. The reason why the readme writing is stalled on my side is because I know the moment all my PR get merged I'll have lot of things to write about. |
Member
Author
|
Any reason not to merge what we have now? It's nice to have it upstream so that when I fix a new thing I can describe it in the README at the same time. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Building on #20. Add information about all the stuff that currently works in the master branch. To be squashed.