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

Remove duplicated section 8.2 in conformance document #406

Closed
RosalynHatcher opened this issue Oct 21, 2022 · 1 comment · Fixed by #442
Closed

Remove duplicated section 8.2 in conformance document #406

RosalynHatcher opened this issue Oct 21, 2022 · 1 comment · Fixed by #442
Labels
defect Conventions text meaning not as intended, misleading, unclear, has typos, format or language errors

Comments

@RosalynHatcher
Copy link
Contributor

RosalynHatcher commented Oct 21, 2022

Title

Remove duplicated section 8.2 in Conformance Document

Moderator

@user

Requirement Summary

When Section 8.2 was renamed from "Compression by Gathering" to "Lossless Compression by Gathering" at CF-1.9 the section got duplicated in the conformance document rather than renamed.

Technical Proposal Summary

Remove section entitled "8.2 Compression by Gathering".

Benefits

Conformance document is updated in line with the Conventions document.

Associated pull request

#407

@RosalynHatcher RosalynHatcher added the defect Conventions text meaning not as intended, misleading, unclear, has typos, format or language errors label Oct 21, 2022
RosalynHatcher pushed a commit to RosalynHatcher/cf-conventions that referenced this issue Oct 21, 2022
@JonathanGregory
Copy link
Contributor

Thanks for opening this issue, Ros @RosalynHatcher, and preparing the pull request to correct it. Much longer than three weeks have passed, so I have merged it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect Conventions text meaning not as intended, misleading, unclear, has typos, format or language errors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants