This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
1 file changed
+2
-2
lines changedLines changed: 2 additions & 2 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
1 | 1 |
| |
2 | 2 |
| |
3 |
| - | |
4 |
| - | |
| 3 | + | |
5 | 4 |
| |
| 5 | + | |
6 | 6 |
| |
7 | 7 |
| |
8 | 8 |
| |
|
1 commit comments
Relequestual commentedon Feb 1, 2017
What did we say about comitting to master? The website doesn't say "manipulate", so not sure where you've gotten this from.
Also, I suggested in #205 that this change should include a section that directs people to the wiki... If you had made a PR rather than commit to master, I would have raised this as a problem.
And no, it's not OK to commit to master because you're not changing the specification. The repo readme is a user facing portal of information, and as such just as important as the actual specification to many.