spec: fix ABNF grammar to use LF token#163
Open
0xheartcode wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Summary
Fix ABNF grammar to use LF token (closes #130)
Section 4.8 defined CRLF = %x0A which contradicts RFC 5234 (where CRLF means %x0D.0A). Renamed the token to LF throughout the grammar to accurately reflect that Git commit messages use LF line endings. Also tightened title from TEXT-NO-LF to 1*TEXT-NO-LF to explicitly reject empty titles, and updated the 72-character guidance to use SHOULD per RFC 2119 convention.
Split from #148 — ABNF fix only, ready to merge immediately. Label normalization tracked separately.
Test plan
make test: all tests pass unchanged