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.

Sign up for GitHub

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

Jump to bottom

(Minor) Substantive changes *must not* be made... (in PR) #43

Closed
iherman opened this issue Jun 5, 2017 · 2 comments
Closed

(Minor) Substantive changes *must not* be made... (in PR) #43

iherman opened this issue Jun 5, 2017 · 2 comments
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) Type: Editorial improvements
Milestone
Process 2018

Comments

@iherman
Copy link
Member

iherman commented Jun 5, 2017

The current draft says, in 6.1.2:

Substantive changes MUST not be made to a Proposed Recommendation

I believe the correct RFC2119 should be:

Substantive changes MUST NOT be made to a Proposed Recommendation
@chaals
Copy link
Contributor

chaals commented Jun 5, 2017

Yep. I doubt I will get to it until next week, so feel free to file a PR, or to wait for me to self-assign which I will do as a sign that I expect to resolve it...

iherman added a commit that referenced this issue Jun 6, 2017
@iherman
Update index.html
f058fc9 
PR to handle issue #43
@iherman iherman mentioned this issue Jun 6, 2017
Merged
@xfq
Copy link
Member

xfq commented Jul 21, 2017

It seems to be fixed by #46. Closing.

@xfq xfq closed this as completed Jul 21, 2017
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) labels Dec 9, 2018
@frivoal frivoal added this to the Process 2018 milestone Feb 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) Type: Editorial improvements
Projects
None yet
Milestone
Process 2018
Development

No branches or pull requests
4 participants
@frivoal @iherman @xfq @chaals