Update the spec to include the line_endings option and trailing newline rules.

Review Request #11768 — Created Aug. 2, 2021 and submitted — Latest diff uploaded

Information

DiffX
master

Reviewers

This introduces a new content option, line_endings, which is used to
define the explicit type of line endings the content uses. This is
primarily important for diff content, due to real-world encounters with
diffs that only appear to be in one form of line ending or another.

Along with this, information on content sections now explicitly state
that the section must end in a newline in the section's encoding.

Built the docs and read through them. Checked that term links were
worked correctly. Checked for spelling errors.

Changes between revision 1 and 2

orig
1
2
3

Commits

Summary ID Author
Update the spec to include the line_endings option and trailing newline rules.
This introduces a new content option, `line_endings`, which is used to define the explicit type of line endings the content uses. This is primarily important for diff content, due to real-world encounters with diffs that only appear to be in one form of line ending or another. Along with this, information on content sections now explicitly state that the section must end in a newline in the section's encoding.
9d23ecd3de5f435856cf57ab0db03fd79b8f6845 Christian Hammond
Update the spec to include the line_endings option and trailing newline rules.
This introduces a new content option, `line_endings`, which is used to define the explicit type of line endings the content uses. This is primarily important for diff content, due to real-world encounters with diffs that only appear to be in one form of line ending or another. Along with this, information on content sections now explicitly state that the section must end in a newline in the section's encoding.
61544c6635a2e0ff2dc0d809d6c6b114b5915305 Christian Hammond
docs/spec/section-format.rst
Loading...